Re: tar commit header names

From: Daniel Barkalow <barkalow@iabervon.org>
Date: Mar 29, 2007, 16:55 UTC
Message-ID: <Pine.LNX.4.64.0703291234090.6485@iabervon.org>
In-Reply-To: <460BE44B.8090301@lsrfire.ath.cx>

On Thu, 29 Mar 2007, René Scharfe wrote:

Show 10 quoted lines

> Daniel Barkalow schrieb:
> > I'm entirely ignorant of pax header stuff, but would it be possible to 
> > have the pax header specify which project this commit is from (which has 
> > to come from a git-archive option, clearly).
> 
> Technically, yes.  The commit ID is stored in a comment, more info could
> appended to it.  Adding more stuff there would necessitate an ordering
> scheme, though.  I'm not sure this is useful enough.  There already is a
> nice convention on where to store the project name, description and URL:
> in a file named 'README'. :)

Ah, and the comment applies until the next comment, so the common prefix of the files in the area with the comment explains it. I was missing what the rules for regions of applicability of pax global headers are. Now, if I could convince... something... to report what comments apply to what files, I'd be set. And that's clearly beyond the scope of git. (Although maybe git-get-... should know how to invoke some other utility on a multiple-project archive once some such tool is known.)

	-Daniel
*This .sig left intentionally blank*