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

Re: Git workflow: how to achieve?

From
Sitaram Chamarty <sitaramc@gmail.com>
Date
Apr 28, 2009, 15:59 UTC
Message-ID
<slrngve9vs.is7.sitaramc@sitaramc.homelinux.net>
In-Reply-To
<20090428140248.31237.qmail@science.horizon.com>
On 2009-04-28, George Spelvin <linux@horizon.com> wrote:
> I want, AT ALL TIMES, to be running the kernel consisting of
> Linus's latest plus my various local hacks.  I want to be able to
> freely update any of the components that make up the result,
> and have the sum automatically recomputed for me.
[and]
> (Because I'm currently organized as a linear list of local
> patches on top of upstream.  I'd prefer separate feature
> branches plus merges, but that's what I'm asking how to make
> work efficiently.)

I'll freely admit I'm focusing on just those two paras out of a fairly long email, but topgit does precisely this. I've started to use it, and it seems to do the job well. When a feature branch gets updated, you just check out what I will call "t/all" and do a "tg update" and it picks up the new stuff.

So the everyday stuff works.

The only sort-of-open question, right now, is how do you remove a dependency when one of your "local hacks" grows up and goes off to college. Er... I mean gets accepted upstream :-)

My guess is that as long as all these local hacks are indeed local, the branch that represents the "sum total" can be blown away and rebuilt when that happens; you'd just list all but the recently graduated feature as dependencies.

Regards,
Sitaram
Previous: Andreas Ericsson
Message 8 of 8 in “Git workflow: how to achieve?”
  1. George SpelvinApr 24, 2009
  2. Uwe Kleine-KönigApr 24, 2009
  3. Andreas EricssonApr 24, 2009
  4. George SpelvinApr 27, 2009
  5. Andreas EricssonApr 28, 2009
  6. George SpelvinApr 28, 2009
  7. Andreas EricssonApr 28, 2009
  8. Sitaram ChamartyApr 28, 2009

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.