Re: git-1.4.0 make problems
- From
Rene Scharfe <rene.scharfe@lsrfire.ath.cx>
- Date
- Jun 17, 2006, 21:55 UTC
- Message-ID
- <44947A43.7070909@lsrfire.ath.cx>
- In-Reply-To
- <7vbqsra4d2.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano schrieb:
Show 16 quoted lines
> I've been using (in my non-git related project aka day-job)
>
> git-tar-tree HEAD^{tree} $(PROJECT)-$(RELNAME) >$(PROJECT)-$(RELNAME).tar
>
> to avoid this. Although all of my target machines have gtar that are
> recent enough so I do not need it, but when the tarball has version
> string in its name, there is not much point having the pax header to
> identify the contents (where the pax header shines is when the result
> does not have the version string in its name).
>
> This might be a sensible thing to do for our dist target as well.
> The product of our dist target is for people who build from the
> source to bootstrap themselves (if they have git, then fetching the
> source using git is preferred anyway), as opposed to using pre-built
> binaries, so being as friendly as we can to different implementations
> of tar is a good thing.Hrm. Is the header really that unfriendly? With a non-POSIX tar you get an extra file and a nice, if somewhat cryptic, reminder to upgrade your archiver. ;-) Seriously, this is way below my annoyance-radar, but I'm obviously biased.
What do you think about the following patch for starters? It adds an example to the git-tar-tree documentation showing your "tree trick" and corrects two formatting buglets.
Signed-off-by: Rene Scharfe <rene.scharfe@lsrfire.ath.cx>
diff --git a/Documentation/git-tar-tree.txt b/Documentation/git-tar-tree.txt index 831537b..c93a8fe 100644 --- a/Documentation/git-tar-tree.txt +++ b/Documentation/git-tar-tree.txt @@ -45,11 +45,16 @@ git tar-tree HEAD | (cd /var/tmp/ && mkd latest commit on the current branch, and extracts it in `/var/tmp/junk` directory. -git tar-tree v2.6.17 linux-2.6.17 | gzip >linux-2.6.17.tar.gz +git tar-tree v2.6.17 linux-2.6.17 | gzip >linux-2.6.17.tar.gz:: Create a tarball for v2.6.17 release. -git tar-tree --remote=example.com:git.git v0.99 >git-0.99.tar +git tar-tree v2.6.17{caret}\{tree\} linux-2.6.17 | gzip >linux-2.6.17.tar.gz:: + + Create a tarball for v2.6.17 release, but without a + global extended pax header. + +git tar-tree --remote=example.com:git.git v0.99 >git-0.99.tar:: Get a tarball v0.99 from example.com.