From: Thomas Rast <trast@student.ethz.ch>
To: Woody Gilk <woody.gilk@kohanaphp.com>
Cc: git@vger.kernel.org, Lars Hjemli <hjemli@gmail.com>
Subject: Re: git-archive and submodules
Date: Mon, 20 Jul 2009 22:56:25 +0200 [thread overview]
Message-ID: <200907202256.26669.trast@student.ethz.ch> (raw)
In-Reply-To: <41ceb5540907200922r5decb047h75e723a1809b587e@mail.gmail.com>
Woody Gilk wrote:
> I would find it hugely valuable if git-archive would support
> submodules, rather than leaving empty files in the place of
> submodules.
Such support was already in the pipeline before 1.6.2, see this
thread:
http://thread.gmane.org/gmane.comp.version-control.git/107030
Lars' series is still available from the repo mentioned in one of the
messages
git://hjemli.net/pub/git/git lh/traverse-gitlinks
but does not merge into master cleanly any more, because an earlier
version of the first commit (of now three) made it into 1.6.2. For
your testing convenience, I rebased the other two commits on 'master'
and pushed them to
git://repo.or.cz/git/trast.git lh/traverse-gitlinks-on-master
All conflicts were trivial, but I made a minor change: there's already
a t5001 from 8aece7f (archive test: attributes, 2009-04-18), so I
renamed it to t5002 in the tip commit.
--
Thomas Rast
trast@{inf,student}.ethz.ch
next prev parent reply other threads:[~2009-07-20 20:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-20 16:22 git-archive and submodules Woody Gilk
2009-07-20 17:33 ` Avery Pennarun
2009-07-20 20:56 ` Thomas Rast [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-10-26 20:37 Anatoly Borodin
2016-10-26 21:04 ` Stefan Beller
2012-04-19 20:10 André Caron
2012-04-20 8:11 ` Jens Lehmann
2012-04-20 18:32 ` Fwd: " André Caron
2012-04-22 18:47 ` Robert Quattlebaum
2013-10-10 14:09 ` Damien Regad
2013-10-10 19:22 ` Amit Bakshi
2008-03-29 13:47 Whit Armstrong
2008-03-29 13:52 ` Shawn O. Pearce
2008-03-29 14:13 ` Whit Armstrong
2008-03-29 21:05 ` CJ van den Berg
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=200907202256.26669.trast@student.ethz.ch \
--to=trast@student.ethz.ch \
--cc=git@vger.kernel.org \
--cc=hjemli@gmail.com \
--cc=woody.gilk@kohanaphp.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).