From: Pedro Rodrigues <prodrigues1990@gmail.com>
To: Fredrik Gustafsson <iveqy@iveqy.com>
Cc: git@vger.kernel.org
Subject: Re: git-archive ignores submodules
Date: Thu, 16 Apr 2015 19:09:47 +0100 [thread overview]
Message-ID: <CAL1ZDKbcmrer481fRY2NEHUQ1J5tjRbHz2yLEcszh3Q-NjcvcQ@mail.gmail.com> (raw)
In-Reply-To: <20150416175623.GJ21868@paksenarrion.iveqy.com>
Good to know about git submodule foreach.
Simpler yet, I'm using:
zip -r ../project.zip . -x *.git*
Which essentially does the same thing I would need from git-archive
--recurse-submodule, zip everything excluding .git folders. Still
would be better to use git itself.
2015-04-16 18:56 GMT+01:00 Fredrik Gustafsson <iveqy@iveqy.com>:
> On Thu, Apr 16, 2015 at 06:35:38PM +0100, Pedro Rodrigues wrote:
>> I've been using git-archive as my main way of deploying to production
>> servers, but today I've come across a git repo with submodules and
>> found out that git archive has no option to include submodules on the
>> output archive.
>
> As far as I know this is an known limitation that's just waiting for
> someone to solve. Thanks for bringing attention to it.
>
>> This simply makes git-archive unusable on this scenario.
>
> Not completely. There's a simple workaround. Combine git submodule
> foreach with git archive and make an archive for each submodule.
>
> Not as simple as if git archive --recurse-submodule would have been
> implementet, but hopefully it can make things work for you at the
> moment.
>
> --
> Fredrik Gustafsson
>
> phone: +46 733-608274
> e-mail: iveqy@iveqy.com
> website: http://www.iveqy.com
--
Pedro Rodrigues
+244 917 774 823
+351 969 042 335
Mail: prodrigues1990@gmail.com
next prev parent reply other threads:[~2015-04-16 18:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 17:35 git-archive ignores submodules Pedro Rodrigues
2015-04-16 17:56 ` Fredrik Gustafsson
2015-04-16 18:09 ` Pedro Rodrigues [this message]
2015-04-16 19:03 ` Jens Lehmann
2015-04-16 19:59 ` Pedro Rodrigues
2015-04-20 8:51 ` Chris Packham
2015-04-19 16:19 ` Kevin Daudt
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=CAL1ZDKbcmrer481fRY2NEHUQ1J5tjRbHz2yLEcszh3Q-NjcvcQ@mail.gmail.com \
--to=prodrigues1990@gmail.com \
--cc=git@vger.kernel.org \
--cc=iveqy@iveqy.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).