From: Nick <oinksocket@letterboxes.org>
To: John Smith <johsmi9933@inbox.com>, git@vger.kernel.org
Subject: Re: Why are submodules not automatically handled by default or at least configurable to do so?
Date: Tue, 27 Oct 2015 10:50:44 +0000 [thread overview]
Message-ID: <562F5704.5070405@letterboxes.org> (raw)
In-Reply-To: <D4E5E890658.000004DCjohsmi9933@inbox.com>
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 possibly about me, as the "Git Advocate"). And they're right, it is
awkward.
Whether or not any sensible default configuration exists, users do need
a way to avoid excessively complicated workflows, or people are just
going to avoid using submodules, or perhaps Git. Hand-rolled solutions
might be better than nothing, but I would expect that this is a common
issue which would benefit from a built-in solution. For instance, so
that one can branch and merge the whole project without duplicating the
work for each submodule.
Am I correct in thinking there isn't anything which does these kind of
things yet?
Thanks!
Nick
next prev parent reply other threads:[~2015-10-27 10:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-25 23:10 Why are submodules not automatically handled by default or at least configurable to do so? John Smith
2015-10-26 0:56 ` Chris Packham
2015-10-26 16:28 ` Stefan Beller
2015-10-26 19:53 ` Junio C Hamano
2015-10-26 4:48 ` Nazri Ramliy
2015-10-26 16:56 ` Jens Lehmann
2015-10-28 7:36 ` Nazri Ramliy
2015-10-27 10:50 ` Nick [this message]
2015-10-27 10:56 ` Davide Fiorentino
2015-10-27 11:40 ` Nick
2015-10-27 12:16 ` Konstantin Khomoutov
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=562F5704.5070405@letterboxes.org \
--to=oinksocket@letterboxes.org \
--cc=git@vger.kernel.org \
--cc=johsmi9933@inbox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.