From: Lars Hjemli <hjemli@gmail.com>
To: Junio C Hamano <gitster@pobox.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: [PATCH 0/2] Add submodule-support to git archive
Date: Sun, 25 Jan 2009 01:52:04 +0100 [thread overview]
Message-ID: <1232844726-14902-1-git-send-email-hjemli@gmail.com> (raw)
This is a cleaned up version of my previous patches which allows git archive
to include submodule content in the archive output.
The main difference between this series and the previous ones is that the
behaviour of `git archive --submodules` are now predictable; the content
included from submodules is defined by the gitlink entries found when
traversing the <tree-ish> specified on the command line, and the set of
submodules to include are defined by specifying either `--submodules=all` or
`--submodules=checkedout` (which is the default mode of operation, i.e. what
you get by only specifying `--submodules`).
To make the `--submodules` option more userfriendly, any submodule repository
discovered during traversal will be registered as an alternate odb (this
will typically be required to make the inter-repository traversal succeed).
Finally, the option `--submodules=group:<name>` is not yet implemented. I
wanted to get these first two patches published early since they define the
semantics of the --submodules option. Adding a 'group' selector on top is
mostly a question of pulling information out of .gitmodules and .git/config,
i.e. not very exciting (but it will be done ;-)
Lars Hjemli (2):
tree.c: allow read_tree_recursive() to traverse gitlink entries
archive.c: add support for --submodules[=(all|checkedout)]
Documentation/git-archive.txt | 5 ++
archive.c | 81 +++++++++++++++++++++++++-
archive.h | 4 +
builtin-ls-tree.c | 9 +--
cache.h | 1 +
merge-recursive.c | 2 +-
sha1_file.c | 11 +++-
t/t5001-archive-submodules.sh | 129 +++++++++++++++++++++++++++++++++++++++++
tree.c | 28 +++++++++
9 files changed, 259 insertions(+), 11 deletions(-)
create mode 100755 t/t5001-archive-submodules.sh
next reply other threads:[~2009-01-25 0:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-25 0:52 Lars Hjemli [this message]
2009-01-25 0:52 ` [PATCH 1/2] tree.c: allow read_tree_recursive() to traverse gitlink entries Lars Hjemli
2009-01-25 0:52 ` [PATCH 2/2] archive.c: add support for --submodules[=(all|checkedout)] Lars Hjemli
2009-01-25 11:57 ` Johannes Schindelin
2009-01-25 13:00 ` Lars Hjemli
2009-01-25 13:55 ` Johannes Schindelin
2009-01-25 11:43 ` [PATCH 1/2] tree.c: allow read_tree_recursive() to traverse gitlink entries Johannes Schindelin
2009-01-25 12:30 ` Lars Hjemli
2009-01-25 4:53 ` [PATCH 0/2] Add submodule-support to git archive Nanako Shiraishi
2009-01-25 8:18 ` Lars Hjemli
2009-01-25 20:35 ` Junio C Hamano
2009-01-25 23:12 ` Lars Hjemli
2009-01-25 23:25 ` Johannes Schindelin
2009-01-26 0:41 ` 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=1232844726-14902-1-git-send-email-hjemli@gmail.com \
--to=hjemli@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--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).