question regarding mercurial

Gé Weijers ge at
Wed Mar 5 09:50:35 CST 2008

On Mar 4, 2008, at 10:22 AM, Mohit Aron wrote:

> 1) How can one pull specific changesets from one repository to  
> another ? It seems mercurial provides good support to pull all  
> changesets up to a given number, but doesn't provide support to  
> pick only a specific changeset and skip earlier ones. This  
> functionality is really important when a release repository is cut  
> out from the main development one, and from thereon only bug fixes  
> need to be merged.

Have you tried the 'transplant' extension. It allows you to merge  
individual patches from another repository.

> 2) It seems one can just modify files without telling mercurial  
> about the intent to do so. And then 'hg status' has to figure out  
> what all is being modified - possibly by doing a 'stat' on each  
> file in the repository. While this might be ok for a local disk,  
> this is terrible for workspaces on NFS. I think future mercurial  
> releases should consider supporting a mode where one needs to  
> explicitly do a 'hg edit filename' to tell mercurial that it is  
> going to modify a file (same as perforce). Any other files that are  
> modified would not show up in 'hg status' - in fact, it might be  
> better if files don't have write permissions unless one does an 'hg  
> edit' on it.

Mercurial does indeed perform a 'stat' on every file in the source  
tree, and that would cause bad performance on NFS. While keeping  
repositories on NFS works it does get pretty slow. This issues is  
common to most if not all DVCSes, and Subversion suffers from it too.  
I clone my workspaces to a local disk, and keep a copy of the  
repository on the file server. I run 'hg push' while I get a cup of  
coffee :-)

Gé Weijers
ge at

-------------- next part --------------
An HTML attachment was scrubbed...

More information about the Mercurial mailing list