From: "Nigel Magnay" <nigel.magnay@gmail.com>
To: "Petr Baudis" <pasky@suse.cz>
Cc: "Johannes Sixt" <j.sixt@viscovery.net>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: git submodules and commit
Date: Wed, 16 Jul 2008 15:31:46 +0100 [thread overview]
Message-ID: <320075ff0807160731g2537780fja1d6f5664163e876@mail.gmail.com> (raw)
In-Reply-To: <20080716141738.GN32184@machine.or.cz>
> 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
next prev parent reply other threads:[~2008-07-16 14:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <320075ff0807160331j30e8f832m4de3e3bbe9c26801@mail.gmail.com>
2008-07-16 10:32 ` git submodules and commit Nigel Magnay
2008-07-16 10:47 ` Johannes Sixt
2008-07-16 11:02 ` Nigel Magnay
2008-07-16 11:35 ` Johannes Sixt
2008-07-16 12:11 ` Petr Baudis
2008-07-16 12:48 ` Nigel Magnay
2008-07-16 13:38 ` Johannes Sixt
2008-07-16 14:03 ` Nigel Magnay
2008-07-16 14:17 ` Petr Baudis
2008-07-16 14:31 ` Nigel Magnay [this message]
2008-07-16 15:43 ` Avery Pennarun
2008-07-17 9:47 ` Nigel Magnay
2008-07-17 15:12 ` Avery Pennarun
2008-07-18 16:11 ` Ping Yin
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=320075ff0807160731g2537780fja1d6f5664163e876@mail.gmail.com \
--to=nigel.magnay@gmail.com \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.net \
--cc=pasky@suse.cz \
/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).