On Fri, Jun 25, 2010 at 01:47:58PM -0400, Chris Ball wrote: > Hi Trevor, > > > Ahh, fixed in my branch now. > > Thanks!
Glad it worked. I hadn't tested it, so the bug is still open... > > Patches attached, since that seems like how we're handling > > changes. Will people push to public branches (or update the > > trunk) so the list-o-patches won't grow too unweildy? > > A simple "it's in my branch now" mail is fine, and I can pull and push > from there to Gitorious (have just done so). It'd be convenient to > use git-send-email to send inline copies of the patches at the same > time, just for review, but that's not necessary -- perhaps just if you > think something in the patch merits notification/review/discussion? Ah, that sounds good. I wouldn't want to inline the CFBE summary to tag migration I just pushed to my branch ;). Also fixed a bug in be list --extra-strings REGEXP so pull whenever ;). -- This email may be signed or encrypted with GPG (http://www.gnupg.org). The GPG signature (if present) will be attached as 'signature.asc'. For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy My public key is at http://www.physics.drexel.edu/~wking/pubkey.txt
pgp5HFGdUUric.pgp
Description: PGP signature
_______________________________________________ Be-devel mailing list [email protected] http://void.printf.net/cgi-bin/mailman/listinfo/be-devel
