From: Linus Torvalds <torvalds@linux-foundation.org>
To: Sergio Callegari <sergio.callegari@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Git archive and trailing "/" in prefix
Date: Thu, 8 Oct 2009 13:35:25 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.01.0910081329570.3432@localhost.localdomain> (raw)
In-Reply-To: <loom.20091008T172303-658@post.gmane.org>
On Thu, 8 Oct 2009, Sergio Callegari wrote:
>
> The git-archive man page indicates that if the --prefix option is passed to
> git-archive, it is compulsory to end the prefix with a "/"
Yeah, that part is intentional. And:
> As a matter of fact, the archiver behaves quite strangely if that slash is
> missing. Files in the root of the working dir are added to the archive with
> their own name modified by the prefix and the same happens for working dir
> sub-directories.
So far so good. But
> However, no file present in the sub-directories, nor sub-sub-directories
> are added.
Ok, that is a bug. It's supposed to just add the prefix to everything, and
it sounds like it's simply broken. I wonder how long it's been broken?
Perhaps forever.
> I would like to know if there some reason why a trailing "/" is not added
> automatically to the prefix when it is missing and the prefix is not empty.
> Would that break anything?
It really was meant to be useful to prefix things without forcing a
directory structure. IOW, being able to use "--prefix=compat-" and just
have everything unpack with their own names, but with the prefix.
Whether anybody uses that, and whether it's worth it, I can't say.
Linus
prev parent reply other threads:[~2009-10-08 20:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-08 15:35 Git archive and trailing "/" in prefix Sergio Callegari
2009-10-08 16:26 ` Junio C Hamano
2009-10-08 22:07 ` Sergio Callegari
2009-10-09 12:49 ` René Scharfe
2009-10-08 16:46 ` René Scharfe
2009-10-09 6:50 ` Junio C Hamano
2009-10-08 20:35 ` Linus Torvalds [this message]
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=alpine.LFD.2.01.0910081329570.3432@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=git@vger.kernel.org \
--cc=sergio.callegari@gmail.com \
/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).