On Jan 30, 11:07 pm, Ben Smith <[email protected]> wrote: > As far as patches go, hg has some features that help manage multiple > patch sets but those look to be more of a maintainer's system rather > than a contributor's system, something like diff -Naur mypyglet/ > pyglet >foo.patch would still probably be the simplest way to generate > a patch for submission. There's more about Mercurial's patch > management > here:http://hgbook.red-bean.com/read/managing-change-with-mercurial-queues...
Mercurial has extensive support to share patches, changes and queues, here's how it works. Patches: hg diff > my.patch hg import --no-commit my.patch Changesets: hg bundle my.bundle remote-repository #this bundles all changesets not found in the remote repository hg unbundle my.bundle #this applies all changesets in the bundle Qeueus: Not going into the minutiae of using queues, but you can share queues by sharing your queue repository (which is just another mercurial repository). One advantage of queues is that a queue push automatically re-merges, which enables you to do continous integration with an upstream of changesets if you work on a patch a long time. -- You received this message because you are subscribed to the Google Groups "pyglet-users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pyglet-users?hl=en.
