git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Re: Publishing "filtered branch repositories" - workflow / recommendations?

From
Heiko Voigt <hvoigt@hvoigt.net>
Date
Dec 9, 2013, 22:59 UTC
Message-ID
<20131209225950.GG9606@sandbox-ub>
In-Reply-To
<CACPiFCJ5hCPvRHB1knvMocN0XdHfSMpbZnqjf7yHAT4mMOSfzw@mail.gmail.com>
On Fri, Dec 06, 2013 at 02:40:15PM -0500, Martin Langhoff wrote:
Show 5 quoted lines
> 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
Previous: Martin LanghoffNext: Junio C Hamano
Message 9 of 13 in “Publishing "filtered branch repositories" - workflow / recommendations?”
  1. Martin LanghoffDec 4, 2013
  2. Martin LanghoffDec 5, 2013
  3. Jens LehmannDec 5, 2013
  4. Martin LanghoffDec 5, 2013
  5. Jens LehmannDec 5, 2013
  6. Martin LanghoffDec 5, 2013
  7. Jens LehmannDec 6, 2013
  8. Martin LanghoffDec 6, 2013
  9. Heiko VoigtDec 9, 2013
  10. Junio C HamanoDec 9, 2013
  11. Jens LehmannDec 11, 2013
  12. Junio C HamanoDec 11, 2013
  13. Heiko VoigtDec 12, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.