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

Re: [TopGit] Multiple concurrent sets of patches

From
MKmartin f krafft <madduck@madduck.net>
Date
Mar 3, 2009, 13:03 UTC
Message-ID
<20090303130316.GA17702@piper.oerlikon.madduck.net>
In-Reply-To
<20090303113741.GO12820@jones.dk>
also sprach Jonas Smedegaard <dr@jones.dk> [2009.03.03.1237 +0100]:
> It seems to me that TopGit is incapable of handling this. That it can 
> only handle patchset against a single branch, and if the need arise for 
> restructuring an additional patchset for e.g. a stable or oldstable 
> branch, then quilt needs to be used manually anyway.

Let me try to understand you: you want TopGit to maintain a single feature branch against two different source branches? How should that work? Could you elaborate a bit so that your needs become a bit more obvious?

Thanks,
-- 
martin | http://madduck.net/ | http://two.sentenc.es/
 
"i feel sorry for people who don't drink. when they wake up in the
 morning, that's as good as they're going to feel all day."
                                                    -- frank sinatra
 
spamtraps: madduck.bogus@madduck.net
Previous: Jonas SmedegaardNext: Jonas Smedegaard
Message 2 of 6 in “[TopGit] Multiple concurrent sets of patches”
  1. Jonas SmedegaardMar 3, 2009
  2. martin f krafftMar 3, 2009
  3. Jonas SmedegaardMar 3, 2009
  4. Uwe Kleine-KönigMar 3, 2009
  5. Jonas SmedegaardMar 3, 2009
  6. martin f krafftMar 4, 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.