BCP for patch submittal

[Bela Babik]

What about using named branches?

- user clones (main repo contains only one branch, which name is "mainline")
- creates a new branch ("mybranch")
- work + commit, whatever
- email the output of
# hg diff --git -r mainline -r mybranch

With this method he can pull and merge anytime.


On 9/20/07, Micah Cowan <micah at cowan.name> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Peter Arrenbrecht wrote:
> > Using mq might be a solution. I at first had my reservations, but by
> > now I just plain love it.
>
> Yes... but doesn't it steepen the learning-curve fairly substantially
> for folks just wanting to submit a few bugfixes or whatever? I'm not
> sure I want to recommend that as a standard practice for casual
> developers (this is a public, Free Software project).
>
> - --
> Micah J. Cowan
> Programmer, musician, typesetting enthusiast, gamer...
> http://micah.cowan.name/
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFG8hmx7M8hyUobTrERCB4EAJsHpaumjNeXfr9C5HZIqqIGxLEDegCfcl2n
> UjHJVWIbxX7bVEH4KRff9Yo=
> =T3UJ
> -----END PGP SIGNATURE-----
> _______________________________________________
> Mercurial mailing list
> Mercurial at selenic.com
> http://selenic.com/mailman/listinfo/mercurial
>