Re: git submodules and commit

From: Nigel Magnay <nigel.magnay@gmail.com>
Date: Jul 16, 2008, 14:31 UTC
Message-ID: <320075ff0807160731g2537780fja1d6f5664163e876@mail.gmail.com>
In-Reply-To: <20080716141738.GN32184@machine.or.cz>

Show 19 quoted lines

> On Wed, Jul 16, 2008 at 03:03:41PM +0100, Nigel Magnay wrote:
>> - All the technical capability is there, it's just the porcelain
>> that's causing the friction.
>> then
>>  would this not seem to be an area that could be improved? Even if it
>> were an optional mode of working?
>
> So, were there already any patches posted to add such a functionality
> that were rejected? If not, apparently noone cared _enough_, yet. ;-)
> You may be the first!
>
> I don't know if there are any _present_ "free developers" willing to
> pick up this task now.  For many (most?) Git developers, submodules
> simply aren't a priority.  For me, they actually currently are, but I
> probably won't want to use them in your way either (even though I can
> agree that your sentiments are valid), so I will personally invest my
> time in doing other things than figuring out the precise semantics
> these operations should have etc.
>

That's cool. I was guessing it might be the case (or alternatively that someone might say 'yeah, but it's 25% of the way there'); my original query was also one of an offer of help ;-) My guess though is that the core-devs have much more connected neural pathways at thinking about the problems around the edge cases to be able to give warnings of 'there be dragons'!

Nigel