From: "René Scharfe" <rene.scharfe@lsrfire.ath.cx>
To: Nick Williams <njw@jarb.freeserve.co.uk>
Cc: git@vger.kernel.org, Junio C Hamano <junkio@cox.net>
Subject: [PATCH] git-archive: document CWD effect
Date: Sun, 08 Apr 2007 14:28:30 +0200 [thread overview]
Message-ID: <4618DFEE.8080707@lsrfire.ath.cx> (raw)
In-Reply-To: <esc64d$d2u$1@sea.gmane.org>
Signed-off-by: Rene Scharfe <rene.scharfe@lsrfire.ath.cx>
---
Nick Williams schrieb:
> git-archive only archives the current working dir (and sub dirs) even
> when no paths are specified. For example, if I do
>
> git archive --format=tar --prefix=git-1.5.0.2/ HEAD > ~/test/test.tar
>
> from with in the Documentation dir, then I only get part of the tree.
>
> Is this the intended behavior?
>
> The reason I ask is that from my (mis)reading of the man page I expect
> to get all of the tree unless paths are specified.
Sorry about the late reply. Would these two additional manpage lines
clear things up for you?
Thanks,
René
diff --git a/Documentation/git-archive.txt b/Documentation/git-archive.txt
index 493474b..b688330 100644
--- a/Documentation/git-archive.txt
+++ b/Documentation/git-archive.txt
@@ -17,6 +17,9 @@ Creates an archive of the specified format containing the tree
structure for the named tree. If <prefix> is specified it is
prepended to the filenames in the archive.
+Only the files and directories in the current working directory are
+included in archives created locally (i.e. without --remote).
+
'git-archive' behaves differently when given a tree ID versus when
given a commit ID or tag ID. In the first case the current time is
used as modification time of each file in the archive. In the latter
next prev parent reply other threads:[~2007-04-08 12:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-03 16:07 bug in git-archive? Nick Williams
2007-03-03 16:09 ` Johannes Schindelin
2007-04-08 12:28 ` René Scharfe [this message]
2007-04-08 23:21 ` [PATCH] git-archive: document CWD effect Junio C Hamano
2007-04-09 15:04 ` René Scharfe
2007-04-09 20:00 ` Junio C Hamano
2007-04-09 20:37 ` Andy Parkins
2007-04-10 14:24 ` René Scharfe
2007-04-10 21:49 ` Junio C Hamano
2007-04-11 20:36 ` René Scharfe
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=4618DFEE.8080707@lsrfire.ath.cx \
--to=rene.scharfe@lsrfire.ath.cx \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=njw@jarb.freeserve.co.uk \
/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).