From: Rene Scharfe <rene.scharfe@lsrfire.ath.cx>
To: Linus Torvalds <torvalds@osdl.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] GIT: Create tar archives of tree on the fly
Date: Sat, 30 Apr 2005 02:13:02 +0200 [thread overview]
Message-ID: <4272CD8E.8040706@lsrfire.ath.cx> (raw)
In-Reply-To: <Pine.LNX.4.58.0504291522250.18901@ppc970.osdl.org>
Linus Torvalds schrieb:
>
> Having just done the git-0.7.tar.gz file with git-tar-tree, I started
> wondering if there is some nice way to encode the commit version
> that got tarred up into the tar archive itself.
The pax archive format allows for comments; you can store the commit ID
in a (archive-)global comment. Archivers are supposed to ignore it and
GNU tar at least does so. You can extract the ID with
$ dd bs=1 skip=523 count=41 2>/dev/null < TARFILE
because it would always end up at that position at the start of the archive.
Rene
next prev parent reply other threads:[~2005-04-30 0:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-26 14:42 [PATCH] GIT: Create tar archives of tree on the fly Rene Scharfe
2005-04-29 22:26 ` Linus Torvalds
2005-04-30 0:13 ` Rene Scharfe [this message]
2005-04-30 1:22 ` Rene Scharfe
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=4272CD8E.8040706@lsrfire.ath.cx \
--to=rene.scharfe@lsrfire.ath.cx \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.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).