git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "René Scharfe" <rene.scharfe@lsrfire.ath.cx>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: git@vger.kernel.org
Subject: Re: tar commit header names
Date: Thu, 29 Mar 2007 18:07:39 +0200	[thread overview]
Message-ID: <460BE44B.8090301@lsrfire.ath.cx> (raw)
In-Reply-To: <Pine.LNX.4.64.0703261230420.6485@iabervon.org>

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'. :)

> Also, could 
> git-get-tar-commit-id have an option to look for more pax headers beyond 
> the first? (I'm building tar files by appending multiple archives for 
> different projects from git-archive, and I suddenly find the embedded 
> commit id is helpful, and surprisingly inaccessible in this context.)

This could be done, at the cost of git-get-tar-commit-id having to be
able to really parse tar files in order to seek to the end of the first
and thus to the start of the appended one.  Right now it simply reads
the first few bytes, quickly checks if this looks like a tar file and
prints the commit ID, if one is found.

The right place to add generic archive comment extraction capabilities
(with multi-archive support) would be a general purpose archiver like
GNU tar, no?

René

  reply	other threads:[~2007-03-29 16:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-26 16:39 tar commit header names Daniel Barkalow
2007-03-29 16:07 ` René Scharfe [this message]
2007-03-29 16:55   ` Daniel Barkalow

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=460BE44B.8090301@lsrfire.ath.cx \
    --to=rene.scharfe@lsrfire.ath.cx \
    --cc=barkalow@iabervon.org \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).