Re: Unexpected behavior in git-rev-list

From: Linus Torvalds <torvalds@osdl.org>
Date: Sep 18, 2005, 17:18 UTC
Message-ID: <Pine.LNX.4.58.0509181013250.26803@g5.osdl.org>
In-Reply-To: <20050918144931.GA9561@ebar091.ebar.dtu.dk>

On Sun, 18 Sep 2005, Peter Eriksen wrote:

Show 29 quoted lines

> 
> There's something I don't quite understand about git-rev-list.
> After adding two files only one shows up with the --objects option.
>
> I can find the difference between the latest commit and it's parent:
> 
> > git diff HEAD^ HEAD
> diff --git a/HS-Plugins/20050403/Recipe b/HS-Plugins/20050403/Recipe
> new file mode 100644
> --- /dev/null
> +++ b/HS-Plugins/20050403/Recipe
> @@ -0,0 +1,16 @@
>  [snip]
> diff --git a/HS-Plugins/20050403/Resources/Dependencies
> b/HS-Plugins/20050403/Resources/Dependencies
> new file mode 100644
> --- /dev/null
> +++ b/HS-Plugins/20050403/Resources/Dependencies
> @@ -0,0 +1,5 @@
>  [snip] 
> 
> Notice that it creates exactly two files.  Now I expect the folllowing
> objects:
> 
> tree HS-Plugins
> tree 20050403
> blob Recipe
> tree Resources
> blob Dependencies

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?

		Linus