Re: Mercurial vs Updated git HOWTO for kernel hackers

From: Petr Baudis <pasky@ucw.cz>
Date: Jun 28, 2005, 15:35 UTC
Message-ID: <20050628153545.GF1275@pasky.ji.cz>
In-Reply-To: <42C16877.6000909@aktzero.com>

Dear diary, on Tue, Jun 28, 2005 at 05:10:47PM CEST, I got a letter where Andrew Thompson <andrewkt@aktzero.com> told me that...

Show 13 quoted lines

> Petr Baudis wrote:
> >>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.
> >
> >"Trunactes"? That sounds very wrong... you mean replace with old
> >version? Anyway, what if the file has same length? It just doesn't make
> >much sense to me.
> 
> I believe this works because the files stored in a binary format that 
> appends new changesets onto the end. Thus, truncating the new stuff from 
> the end effectively removes the commit.

Yes, I'm sorry - I missed the "repo" part and thought that was what it was doing with the checked out files. ;-)

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
<Espy> be careful, some twit might quote you out of context..