I'm not an expert, I'm still learning more about it. I think you're talking about day-to-day use, and work flow?
Mercurial can be used in the same sort of work flow as SVN - checkout, commit, update - the version control things we know and love. Committers apply patches and changes they made to the appropriate branch and commit them. * Check out the tip revision into the pyglet folder: hg clone https://pyglet.googlecode.com/hg/ pyglet cd pyglet * Make some changes and commit them edit somefile hg commit -m "I changed somefile" * Grab any other updates from the head of the repository hg pull * Apply those changes to your working copy (hg pull does not do this automatically, may depend on your hg client) hg update * Publish your changes to google code: hg push * Switch to a different branch/tag hg update -r pyglet-1.1-maintenance The separate pull and update steps and the separate commit and push steps are what will noticeably differ from SVN, off the bat. Initially I see things going this way. Committers apply patches and changes they made. Possibly we'll see some more collaboration along the lines of Florian Bösch's mercurial repository, where Florian has made some patches. A committer can pull whatever they'd like from there and push it up to google code. There's branching and merging, like you'd expect, and some more sophisticated features that may be useful, such as Mercurial Queues. I don't know yet, some of this will depend on how development and contributions happen in the future. -b On Jan 29, 6:41 pm, Richard Jones <[email protected]> wrote: > On 30/01/2010, at 12:55 PM, Ben Smith wrote: > > > If you have the mercurial command line client, it's > > > hg clonehttps://pyglet.googlecode.com/hg/pyglet > > > Pointers to other clients and resources are here: > >http://code.google.com/p/pyglet/source/checkout > > For the benefit of those of us who have never used such a system how do you > see the project using this new source repository? Please include working > commands. > > Richard -- 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.
