From: Heiko Voigt <hvoigt@hvoigt.net>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: Jens Lehmann <Jens.Lehmann@web.de>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Re: Publishing "filtered branch repositories" - workflow / recommendations?
Date: Mon, 9 Dec 2013 23:59:50 +0100 [thread overview]
Message-ID: <20131209225950.GG9606@sandbox-ub> (raw)
In-Reply-To: <CACPiFCJ5hCPvRHB1knvMocN0XdHfSMpbZnqjf7yHAT4mMOSfzw@mail.gmail.com>
On Fri, Dec 06, 2013 at 02:40:15PM -0500, Martin Langhoff wrote:
> On Fri, Dec 6, 2013 at 3:48 AM, Jens Lehmann <Jens.Lehmann@web.de> wrote:
> > Right you are, we need tutorials for the most prominent use cases.
>
> In the meantime, are there any hints? Emails on this list showing a
> current "smart" workflow? Blog posts? Notes on a wiki?
None that I know of mainly because we have not yet reached the goal we
are aiming at. Maybe we should write something, A few points from
$dayjob that come to my mind:
* A submodule commit is only allowed to be merged into master in a
superproject commit if it is merged into master (or a stable branch)
in the submodule. That way you ensure that any submodules commits
that are tracked in a superproject are contained in each other and
can be cleanly merged. (no rewinds, one commit contains the other)
* Submodule should be selfcontained (i.e. if its a library have tests
that use the code you implement). That way changes in the submodule
can be made independent from the superproject
* If a submodule needs another submodule have them side by side
instead of one inside another. See the next point for explanation.
* Only one depth of recursion for submodules. Even though intuition
tell you that if some submodule needs another it should contain the
other its IMO not wise to do so. There will be times when some other
submodule needs the same submodule that is contained in the other
and then you end up with two copies of the same code. My suggestion:
Let the superproject bundle all the dependencies between modules.
* Submodules are a good solution for shared code where the dependency
goes superproject needs submodule. If you divide code into
submodules because of access control and the dependency is actually
that the submodule needs the superproject it works but is less than
optimal.
Thats what I can quickly suggest and probably far from complete.
Cheers Heiko
next prev parent reply other threads:[~2013-12-09 23:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-04 23:01 Publishing "filtered branch repositories" - workflow / recommendations? Martin Langhoff
2013-12-05 18:43 ` Martin Langhoff
2013-12-05 19:18 ` Jens Lehmann
2013-12-05 19:27 ` Martin Langhoff
2013-12-05 19:54 ` Jens Lehmann
2013-12-05 22:06 ` Martin Langhoff
2013-12-06 8:48 ` Jens Lehmann
2013-12-06 19:40 ` Martin Langhoff
2013-12-09 22:59 ` Heiko Voigt [this message]
2013-12-09 23:56 ` Junio C Hamano
2013-12-11 22:03 ` Jens Lehmann
2013-12-11 23:16 ` Junio C Hamano
2013-12-12 13:39 ` Heiko Voigt
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=20131209225950.GG9606@sandbox-ub \
--to=hvoigt@hvoigt.net \
--cc=Jens.Lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=martin.langhoff@gmail.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 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).