Message-ID: <4530B897.3010403@lsrfire.ath.cx>
Date: Sat, 14 Oct 2006 12:14:47 +0200
From: Rene Scharfe <rene.scharfe@lsrfire.ath.cx>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Shawn Starr <shawn.starr@rogers.com>, Linus Torvalds <torvalds@osdl.org>
CC: linux-kernel mailing list <linux-kernel@vger.kernel.org>,
       "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: bzip2 tarball 2.6.19-rc2 packaged wrong?
References: <200610132336.21392.shawn.starr@rogers.com>
In-Reply-To: <200610132336.21392.shawn.starr@rogers.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1052
Lines: 30

Shawn Starr schrieb:
> Linus, something in git  broke the prepackaged tarball/bzip2 generation?
> 
> $ tar -jxvf linux-2.6.19-rc2.tar.bz2
> linux-2.6.19-rc2.gitignore
> linux-2.6.19-rc2COPYING
> linux-2.6.19-rc2CREDITS
> linux-2.6.19-rc2Documentation/
> linux-2.6.19-rc2Documentation/00-INDEX
> linux-2.6.19-rc2Documentation/ABI/
> linux-2.6.19-rc2Documentation/ABI/README
> 
> -rc1 was ok.

Perhaps tar generation has been switched to using git-archive instead of
git-tar-tree?  There's an, admittedly, subtle difference in how the two
handle prefixes/basedirs.  The following two commands do the same:

   $ git-tar-tree rev basedir
   $ git-archive --prefix=basedir/ rev

If you use --prefix and you want a base directory then you have to
provide your own slash (basedir = prefix + path_separator).

Ren?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/