preliminary guide to Mercurial via workflows

[Arne Babenhauserheide]

Am Donnerstag 30 April 2009 15:26:32 schrieb David I.:
> > At this point, your fix is merged with all your other work, 
> > and you can just
> > go on coding. Additionally the history shows clearly where you 
> > fixed the bug,
> > so you'll always be able to check where the bug was.
>
> Should you advise to update to tip now? Could I possibly be basing more
> code on the old revision if I just "go on coding?"

After the merge we should already be at (the new) tip, sicne that's the only 
other head, so advertising the update would not help, I think. Or did I 
stumble over some misunderstanding here? 

I just tried the workflow myself (update to a revision before I did a file 
copy, fix a bug there and then merge it with tip), and it worked quite well 
(both copies of the file now include the fix). 

Best wishes, 
Arne

--- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- 
   - singing a part of the history of free software -
              http://infinite-hands.draketo.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
Url : http://selenic.com/pipermail/mercurial/attachments/20090501/e91dad21/attachment.pgp