lkml.org 
[lkml]   [2005]   [Jun]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Mercurial vs Updated git HOWTO for kernel hackers
On Fri, Jun 24, 2005 at 08:41:01AM +0200, Petr Baudis wrote:
> > 5.1) undo the last commit or pull
> >
> > $ hg undo
>
> $ cg-admin-uncommit
>
> Note that you should never do this if you already pushed the changes
> out, or someone might get them. (That holds for regular Git too.) See
>
> $ cg-help cg-admin-uncommit # (or cg-admin-uncommit --help)
>
> for details. (That's another Cogito's cool feature. Handy docs! ;-)
>

Does it still works if the last commit was interrupted or due to error for some
reason? Undo pull is pretty cool because you might pull a lot of commit
in one blow. Get rid of commit one by one is going to be painful. Some times
the object you pull has more than one chain of history it will be very nasty
if you want to clean it up.

Mercurial's undo is taking a snapshot of all the changed file's repo file length
at every commit or pull. It just truncate the file to original size and undo
is done.

Chris

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-06-24 18:02    [W:0.514 / U:1.116 seconds]
©2003-2014 Jasper Spaans. Advertise on this site