From: Lars Hjemli <hjemli@gmail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>
Subject: [RFC/PATCH 2/3] archive.c: enable traversal of submodules
Date: Mon, 12 Jan 2009 00:45:54 +0100 [thread overview]
Message-ID: <1231717555-10559-3-git-send-email-hjemli@gmail.com> (raw)
In-Reply-To: <1231717555-10559-2-git-send-email-hjemli@gmail.com>
The option --submodules can be used to activate traversal of sub-
modules when creating archives.
Signed-off-by: Lars Hjemli <hjemli@gmail.com>
---
archive.c | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/archive.c b/archive.c
index 9ac455d..973dde4 100644
--- a/archive.c
+++ b/archive.c
@@ -262,6 +262,8 @@ static int parse_archive_args(int argc, const char **argv,
OPT_STRING(0, "format", &format, "fmt", "archive format"),
OPT_STRING(0, "prefix", &base, "prefix",
"prepend prefix to each pathname in the archive"),
+ OPT_BOOLEAN(0, "submodules", &traverse_gitlinks,
+ "include reacheable submodules"),
OPT__VERBOSE(&verbose),
OPT__COMPR('0', &compression_level, "store only", 0),
OPT__COMPR('1', &compression_level, "compress faster", 1),
--
1.6.1.81.g1df1.dirty
next prev parent reply other threads:[~2009-01-12 0:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-11 23:45 [RFC/PATCH 0/3] Enable in-process submodule traversal Lars Hjemli
2009-01-11 23:45 ` [RFC/PATCH 1/3] tree.c: add support for traversal of submodules Lars Hjemli
2009-01-11 23:45 ` Lars Hjemli [this message]
2009-01-11 23:45 ` [RFC/PATCH 3/3] builtin-ls-tree: enable " Lars Hjemli
2009-01-12 3:15 ` [RFC/PATCH 1/3] tree.c: add support for " Junio C Hamano
2009-01-12 9:04 ` Lars Hjemli
2009-01-12 10:07 ` Junio C Hamano
2009-01-12 10:59 ` Lars Hjemli
2009-01-12 2:07 ` [RFC/PATCH 0/3] Enable in-process submodule traversal Junio C Hamano
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=1231717555-10559-3-git-send-email-hjemli@gmail.com \
--to=hjemli@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).