From: Michael Witten <mfwitten@mit.edu>
Date: Fri, 19 Oct 2007 02:29:28 GMT
Subject: Re: Proposed git mv behavioral change
Message-ID: <A2491F60-A00E-412A-8389-1C9EB5EDFCEF@mit.edu>
In-Reply-To: <20071019021618.GE3290@coredump.intra.peff.net>


On 18 Oct 2007, at 10:15:29 PM, Shawn O. Pearce wrote:
> git-add amounts to either inserting a new path->stat/sha1 entry
> in the index, or updating an existing entry with new stat/sha1
> information.
>
> git-rm amounts to removing a path->stat/sha1 entry from the index.
> It's just gone once the git-rm is completed.  As if it was never
> there to begin with.
>
> A git-commit (really git-write-tree but same difference to the
> end-user) stores whatever is in the index as the gospel truth for
> how that commit's files should appear.

Ah. Basically my 'pseudo-code' is correct, but redundant.


On 18 Oct 2007, at 10:16:18 PM, Jeff King wrote:
> Eh? The changes will make it into history when you commit. Or  
> perhaps I
> don't understand your question. Can you rephrase it?

I misunderstood the (lack) of details.

On 18 Oct 2007, at 10:15:29 PM, Shawn O. Pearce wrote:
> But its all really as simple as it seems.

It's about time I read more thoroughly through the manual!

Thanks.