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

Re: topgit patches

From
Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Date
Feb 26, 2009, 14:15 UTC
Message-ID
<20090226141548.GA32439@pengutronix.de>
In-Reply-To
<20090226060652.GA16251@lapse.rw.madduck.net>
Hi Martin,
On Thu, Feb 26, 2009 at 07:06:52AM +0100, martin f krafft wrote:
Show 9 quoted lines
> also sprach Uwe Kleine-König <u.kleine-koenig@pengutronix.de> [2009.02.26.0015 +0100]:
> > Well, I already wondered if there is someone using topgit apart
> > from me. :-)
> 
> I use it and would like to actively maintain it, but time is short
> and I wanted to push out a new option parser with 0.6, but it's just
> not finished yet. As soon as I find a few hours, I'll try to revisit
> it. But if someone else has the time, maybe we can prepare a 0.6
> without a new option parser?
If you need help, I'm also interested to co-maintain the debian package.
Just an offer ...  (I don't know the exact way to become a maintainer,
if I need to meet a Debian developer, that's no problem, I know one.)
 
> > Given this situation it probably doesn't make sense to describe
> > some problems I currently see using topgit :-|.
> 
> Please do, I am interested.

Sometimes I get an error about being unable to delete a temp file, will try to track that down when it happens next.

Having many topgit controlled patches it's hard to get the overview. Updating patches with many interdependencies is hard and doing a merge wrong is hard to detect and fix. I don't have a good idea for that yet, but I will investigate some thought here.

Further ideas and plans of mine in no particular order:
 1 move all or most topgit-topic-branches to a private namespace, say
   refs/top-heads because the patch branches pollute the output of git
   branch.
 2 export method that works like the existing linearize but creates
   branches for topgit branches living in refs/heads and merges these
   properly without linearisation.
   (obviously depends on 1)
 3 address topgit bugs on bugs.debian.org
 4 factor out some code to helper functions in tg.sh
 5 convice my colleagues that topgit is the right tool to gain world
   domination :)
 6 I'm sure I will find some more while doing 1 to 5. :)

Best regards Uwe

-- 
Pengutronix e.K.                              | Uwe Kleine-König            |
Industrial Linux Solutions                    | http://www.pengutronix.de/  |
Previous: martin f krafftNext: martin f krafft
Message 12 of 16 in “topgit patches”
  1. Uwe Kleine-KönigFeb 25, 2009
  2. [TOPGIT] limit rev-list in branch_contains to a single revUwe Kleine-König, Feb 25, 2009
  3. [TOPGIT] allow working with annihilated branchesUwe Kleine-König, Feb 25, 2009
  4. [TOPGIT] make tg remote idempotentUwe Kleine-König, Feb 25, 2009
  5. [TOPGIT] make creating a commit from a topgit branch a functionUwe Kleine-König, Feb 25, 2009
  6. [TOPGIT] implement linearize export methodUwe Kleine-König, Feb 25, 2009
  7. Petr BaudisFeb 25, 2009
  8. Uwe Kleine-KönigFeb 25, 2009
  9. Petr BaudisFeb 25, 2009
  10. Uwe Kleine-KönigFeb 26, 2009
  11. martin f krafftFeb 26, 2009
  12. Uwe Kleine-KönigFeb 26, 2009
  13. martin f krafftFeb 27, 2009
  14. Uwe Kleine-KönigFeb 27, 2009
  15. Uwe Kleine-KönigMar 2, 2009
  16. martin f krafftMar 3, 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.