Mercurial workflow

A few days ago, I posted here about the basics of working with mercurial. A little after that, Tor Norbye, from Sun Microsystems and The Java Posse, posted about his workflow with mercurial, a few problems he had with it, and how he solved these issues. I really like what he said, and I’m considering using the suggested workflow. If you are interested, take a look at his post.

The main issue is related to the fact that, more often than not, we need to commit part of the files we have changed in our projects, because we might be working on several things at the same time, and only one of them of ready to be committed.

But mercurial doesn’t seem to like this. So, to sum up the approach Tor now uses, you can work with two local repositories: one with the actual changes, and one exclusively to do the commits. When it is “commit time”, you “send” the files to be committed from the working repository to the commit one. See his post for the details.

I’ll try that out, let’s see how it feels 🙂

Advertisements
This entry was posted in misc and tagged . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s