Re: Why are submodules not automatically handled by default or at least configurable to do so?

On Tue, Oct 27, 2015 at 12:56 AM, Jens Lehmann wrote: > Which seems a bit error prone as you could forget to update the submodules > and build incorrect rpms from them, or am I missing something? For my case I'm not building the rpms directly after merging in the fixes done

Re: Why are submodules not automatically handled by default or at least configurable to do so?

I too am interested in finding ways to automate working with submodules, as it's a particular pain point with my colleagues. They frequently shoot themselves in the foot trying to branch and merge a project with submodules, resulting in a broken build and grumpy comments about git (or

Re: Why are submodules not automatically handled by default or at least configurable to do so?

Why not set alias(es) for that? Best, Davide > On 27 Oct 2015, at 10:50, Nick wrote: > > I too am interested in finding ways to automate working with submodules, as > it's a particular pain point with my colleagues. They frequently shoot > themselves in the foot

Re: Why are submodules not automatically handled by default or at least configurable to do so?

On Tue, 27 Oct 2015 11:40:15 + Nick wrote: > > Why not set alias(es) for that? [...] > But oh yes, there is another difficulty with aliases. Eclipse users > on Windows: [...] Not to counter your actual argument, but AFAIK EGit uses JGit which is a Java

Re: Why are submodules not automatically handled by default or at least configurable to do so?

On 27/10/15 10:56, Davide Fiorentino wrote: Why not set alias(es) for that? That counts as a hand-rolled (i.e. ad-hoc) solution. So not out of the question, but I'd rather point my colleagues at something tried and tested, rather than simply re-invent wheels, possibly badly. I'd be

Re: Why are submodules not automatically handled by default or at least configurable to do so?

Stefan Beller writes: > IIUC at the time submodules were invented, there was need for lots of > code to be written. > Each command needed new code to deal with submodules. As there was not > enough people/time > to do it properly, the "do nothing" was the safest action which

Re: Why are submodules not automatically handled by default or at least configurable to do so?

Am 26.10.2015 um 05:48 schrieb Nazri Ramliy: On Mon, Oct 26, 2015 at 7:10 AM, John Smith wrote: When would people routinely check out a branch and want to stay with the submodules as the have been checked out for the old branch? I do this a lot. At my $dayjob we have a

Re: Why are submodules not automatically handled by default or at least configurable to do so?

On Sun, Oct 25, 2015 at 5:56 PM, Chris Packham wrote: > On Mon, Oct 26, 2015 at 12:10 PM, John Smith wrote: >> I found that I use submodules much, much more often in my git projects than >> I used externals >> in Subversion and the reason is that

Why are submodules not automatically handled by default or at least configurable to do so?

I found that I use submodules much, much more often in my git projects than I used externals in Subversion and the reason is that git encourages/forces to organize large projects into smaller repositories, one reason for this being that subversion allows to check out parts of a repository

Re: Why are submodules not automatically handled by default or at least configurable to do so?

On Mon, Oct 26, 2015 at 12:10 PM, John Smith wrote: > I found that I use submodules much, much more often in my git projects than I > used externals > in Subversion and the reason is that git encourages/forces to organize large > projects into > smaller repositories, one

Re: Why are submodules not automatically handled by default or at least configurable to do so?

On Mon, Oct 26, 2015 at 7:10 AM, John Smith wrote: > When would people routinely check out a branch and want to stay with the > submodules as > the have been checked out for the old branch? I do this a lot. At my $dayjob we have a super project with bunch of sub projects.