From: Linus Torvalds <torvalds@osdl.org>
To: Keith Owens <kaos@ocs.com.au>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.12
Date: Fri, 17 Jun 2005 23:05:28 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0506172255280.2268@ppc970.osdl.org> (raw)
In-Reply-To: <21446.1119073126@ocs3.ocs.com.au>
On Sat, 18 Jun 2005, Keith Owens wrote:
> On Fri, 17 Jun 2005 22:13:25 -0700 (PDT),
> Linus Torvalds <torvalds@osdl.org> wrote:
> >As some people may have noticed already, 2.6.12 is out there now.
>
> tar xjvf linux-2.6.12.tar.bz2, using SuSE tar-1.13.25-325.3 on IA64,
> reports
>
> tar: pax_global_header: Unknown file type 'g', extracted as normal file
>
> It does not seem to cause any problems.
Yes, git creates tar-archives that use the extended pax headers, and I
think you need tar-1.14 to fully understand them. They should not hurt
(apart from the warning) on older versions of tar.
The extended header just contains a hidden comment record that tells the
git commit ID that was used to generate the tar-tree.
Because it's extracted as a regular file (instead of tar knowing that it's
a comment header), you will now have a file called "pax_global_header"
that has the contents
52 comment=9ee1c939d1cb936b1f98e8d81aeffab57bae46ab
in it (where "9ee1c939d1cb936b1f98e8d81aeffab57bae46ab" is the git SHA1
name of the Linux-2.6.12 commit).
So it's not entirely "harmless" in that it causes a bogus file to be
created, but it's not like it's a huge problem either, and that bogus file
actually does contain real information (although it's not useful unless
you're a git user).
Linus
next prev parent reply other threads:[~2005-06-18 6:03 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-18 5:13 Linus Torvalds
2005-06-18 5:38 ` Keith Owens
2005-06-18 6:05 ` Linus Torvalds [this message]
2005-06-18 6:59 ` Willy Tarreau
2005-06-18 10:36 ` Jesper Juhl
2005-06-18 10:48 ` Alexey Dobriyan
2005-06-18 10:52 ` Jesper Juhl
2005-06-18 10:54 ` Brice Goglin
2005-06-18 17:42 ` Linus Torvalds
2005-06-18 18:26 ` Steven Rostedt
2005-06-21 14:32 ` [RFC: 2.6 patch] better USB_MON dependencies Adrian Bunk
2005-06-21 19:35 ` Pete Zaitcev
2005-06-21 21:04 ` Adrian Bunk
2005-06-23 9:36 ` [2.6 " Adrian Bunk
2005-06-25 20:15 ` Pete Zaitcev
2005-06-25 21:32 ` Adrian Bunk
2005-06-18 19:05 Linux 2.6.12 Nick Warne
2005-06-18 19:20 ` Jim Crilly
2005-06-18 19:33 ` Jesper Juhl
2005-06-19 1:39 ` aq
2005-06-19 1:48 ` David Lang
2005-06-19 2:36 ` randy_dunlap
2005-06-19 9:29 ` Ian Campbell
2005-06-19 15:00 ` aq
2005-06-20 9:36 ` Vincent Hanquez
2005-06-20 21:55 ` Matt Mackall
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=Pine.LNX.4.58.0506172255280.2268@ppc970.osdl.org \
--to=torvalds@osdl.org \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®