On Wed, Apr 16, 2008 at 3:54 PM, Steve Borho <[EMAIL PROTECTED]> wrote: > > > On Wed, 2008-04-16 at 16:28 +0200, Joeri Belis wrote: > > I am trying to understand all the feature of the sofware. But i ran > > into an strange problem. > > > > > > > > 2 persons working on a project using a centralized repo. Both have > > up-to-date repo's local. Person 1 choses the option from the menu to > > "Update To Revision". So Person 1 now has a different file then person > > 2. Person 1 tries to commit after the "Update To Revision", but > > according to the software there is nothing to commit?? > > > > > > > > Now there are 2 different version and person 1 can't commit the > > revision back to the centralized repo. > > > > > > > > What did i missunderstand? > > I suggest you read the hgbook in order to better understand the > Mercurial itself. Committing is always done relative to your working > directory parent revision (the revision you have checked out / updated). > > http://hgbook.red-bean.com/
In case hgbook is too 'heavy', you can check out this intro on Mercurial wiki, which explains the concepts without the burden of all those hg commands: http://www.selenic.com/mercurial/wiki/index.cgi/UnderstandingMercurial ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Tortoisehg-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
