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

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

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 9, 2013, 23:56 UTC
Message-ID
<xmqqhaahvas2.fsf@gitster.dls.corp.google.com>
In-Reply-To
<20131209225950.GG9606@sandbox-ub>
Heiko Voigt <hvoigt@hvoigt.net> writes:
Show 16 quoted lines
> 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)

I think this is closely related to Martin's list of wishes we earlier saw in the thread: remind the user to push necessary submodule tip before the top-level commit that needs that commit in the submodule is pushed out. Giving projects a way to implement such a policy decision would be good, and having a default policy, if we can find one that would be reasonable for any submodule users, would be even better. Would adding a generic pre-push hook at the top-level sufficient for that kind of thing, I have to wonder.

Previous: Heiko VoigtNext: Jens Lehmann
Message 10 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.