On Fri, Apr 17, 2015 at 7:59 AM, Pedro Rodrigues
wrote:
> Not completely off topic, but for consistency consider that:
> git-clone supports --recursive and --recurse-submodules, which do the
> same thing.
> git-pull and git-push only support --recurse-submodules.
It took a while to get the term
On Thu, Apr 16, 2015 at 09:03:10PM +0200, Jens Lehmann wrote:
> Am 16.04.2015 um 20:09 schrieb Pedro Rodrigues:
>
> If people are interested I could try to polish it and resubmit it.
> It would be great if Pedro could test that it does what he expects.
I'm certainly interested.
--
To unsubscribe
I sure can. Just send me an ID I can pull and test in here (not really
into C, so this the least I can contribute).
Although, my expectations are very simple, I just expect(ed) the exact
same git-archive command to be run on submodule(s), and have an output
on a single zip|tar|whatever file.
Not
Am 16.04.2015 um 20:09 schrieb Pedro Rodrigues:
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 bet
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
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
6 matches
Mail list logo
