[Slackbuilds-users] xmobar, p4
Chess Griffin
chess at chessgriffin.com
Fri Jun 4 01:43:32 UTC 2010
On Wed, 2 Jun 2010 21:19:21 -0300
Max Miorim <miorimmax at gmail.com> wrote:
> On Wed, Jun 2, 2010 at 8:31 PM, R. Andrew Bailey <bailey at akamai.com>
> wrote:
> > Hi All,
> >
> > I discussed this with vbatts a little today, and we agreed it was
> > probably best to just send this to the list and see if it sticks to
> > the wall.
> >
> > I have a clone/branch/fork whatever of the canonical sbo
> > repository, and have merged a pair of my own branches into it. One
> > is a new package "p4", which is almost absurd to package since its
> > a single binary and a manpage. The other is an update to xmobar,
> > which I think is abandoned.
> >
> > Both commits are at:
> >
> > git://github.com/GooseYArd/slackbuilds.git
> >
> > xmobar 0.11.1: e83d5d1cdac63185666a
> > p4 r0.9.2: 419ff27d9116a48dc1ca
> >
> > I'm not sure when making a pull request whether I ought to be
> > sending the commit for the merge or the commit on the branch I
> > submitted the file additions to. Maybe one of the admins on the
> > list can confirm whether this is workable?
> >
> > Thanks,
> >
> > .andy
>
> If I'm not mistaken, for now, submissions will go through the form and
> trivial fixes _might_ get pulled from our repositories (depends on
> who's reviewing it).
>
> Have a look at this email from Robby:
> http://lists.slackbuilds.org/pipermail/slackbuilds-users/2010-May/005627.html
>
> -- Max
>
> PS: I'm not an admin. :P
I am testing the xmobar update and assuming it works ok, I'll commit it
to my branch. Thanks.
--
Chess Griffin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20100603/610dab7f/attachment.asc>
More information about the SlackBuilds-users
mailing list