Re: Unexpected behavior in git-rev-list

From: Peter Eriksen <s022018@student.dtu.dk>
Date: Sep 18, 2005, 17:58 UTC
Message-ID: <20050918175847.GA10427@ebar091.ebar.dtu.dk>
In-Reply-To: <Pine.LNX.4.58.0509181013250.26803@g5.osdl.org>

On Sun, Sep 18, 2005 at 10:18:10AM -0700, Linus Torvalds wrote:

Show 6 quoted lines

> 
> 
> On Sun, 18 Sep 2005, Peter Eriksen wrote:
> > 
> > There's something I don't quite understand about git-rev-list.
> > After adding two files only one shows up with the --objects option.

...

Show 7 quoted lines

> Well, it looks like some other file has _exactly_ the same contents as the 
> new "Dependencies", which means that git notices that the blob isn't 
> actually new.
> 
> Which doesn't surprise me at all - you've got a lot of projects there that 
> seem to have a Dependencies thing. Why wouldn't some other project have 
> the exact same ones?

Ah! You are right, there is a Dependencies file in each of the 1000+ directories and they are generated from almost the same setup, so it must be that there is another one like the one, I just commited. That explains it. Now I will try to see, if I actually can get the effect I expected somehow. :-)

So my new challenge to myself: Given two commit objects A and B list all the tree and blob objects which are not in both A and B.

After that I think writing a command which does the same as 'cvs annotate' would be a good exercise.

Thanks for the explanation.

Regards,

Peter

P.S. I'm on the list, so it's not necessary to cc me.