Re: [PATCH] git-http-fetch: Allow caching of retrieved objects byproxy servers

From: Petr Baudis <pasky@suse.cz>
Date: Sep 19, 2005, 13:35 UTC
Message-ID: <20050919133508.GA2903@pasky.or.cz>
In-Reply-To: <432E91ED.7050605@b-i-t.de>

Dear diary, on Mon, Sep 19, 2005 at 12:24:45PM CEST, I got a letter where sf <sf@b-i-t.de> told me that...

Show 15 quoted lines

> >remember that git objects are identified by their sha1, if the sha1 is 
> >what you want (and the file matches the sha1 after you decompress it) 
> >then it really doesn't matter what it's on-disk representation is.
> 
> You are arguing on the git tool level but we are talking about HTTP 
> which knows nothing about the uncompressed sha1.
> 
> The OP assumed that "files in a GIT repository are immutable" which is 
> not true. If you consider the sequence
> 
> pack -> prune -> update zlib or git -> unpack
> 
> you can end up with different files if the new zlib implementation 
> changes imcompatibly (with respect to byte-by-byte compression results) 
> or if git suddenly does not use the default compression level any more.

Yes, but why should this matter? It shouldn't matter if you get the old "version" or the new version of the file over HTTP, the actual object's contents is still the same, and GIT shouldn't care.

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
If you want the holes in your knowledge showing up try teaching
someone.  -- Alan Cox