All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rene Scharfe <rene.scharfe@lsrfire.ath.cx>
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?
Date: Sat, 14 Oct 2006 12:14:47 +0200	[thread overview]
Message-ID: <4530B897.3010403@lsrfire.ath.cx> (raw)
In-Reply-To: <200610132336.21392.shawn.starr@rogers.com>

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é

  parent reply	other threads:[~2006-10-14 10:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-14  3:36 bzip2 tarball 2.6.19-rc2 packaged wrong? Shawn Starr
2006-10-14  4:48 ` Grant Coady
2006-10-14 10:14 ` Rene Scharfe [this message]
2006-10-14 18:53 ` Linus Torvalds

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=4530B897.3010403@lsrfire.ath.cx \
    --to=rene.scharfe@lsrfire.ath.cx \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shawn.starr@rogers.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.