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

using stgit/guilt for public branches

From
MTMichael S. Tsirkin <mst@dev.mellanox.co.il>
Date
Apr 25, 2007, 12:20 UTC
Message-ID
<20070425122048.GD1624@mellanox.co.il>

Hi! On git.openfabrics.org we use git to manage all code for our OFED distribution. For our kernel code we basically started with 2.6.20, and add some patches, which we currently keep separate from upstream kernel source - this makes it possible to update from upstream and extract the patches to post them for upstream inclusion easily.

On the surface, it looks like using stg or guilt would be a good idea for us, however multiple people need to collaborate on the patch series.

I am concerned that publishing a git branch managed by stg/guilt would present problems: it seems that every time patches are re-ordered, a patch is re-written or removed, or we update from upstream, everyone who pulls the tree branch will have a hard-to-resolve conflict.

Is that really a problem? If so, would it be possible to work around this somehow?
Thanks,
-- 
MST
Next: Josef Sipek
Message 1 of 12 in “using stgit/guilt for public branches”
  1. Michael S. TsirkinApr 25, 2007
  2. Josef SipekApr 25, 2007
  3. Michael S. TsirkinApr 25, 2007
  4. Josef SipekApr 25, 2007
  5. Robin RosenbergApr 25, 2007
  6. Yann DirsonMay 3, 2007
  7. Robin RosenbergMay 3, 2007
  8. Robin RosenbergMay 3, 2007
  9. Yann DirsonMay 4, 2007
  10. Michael S. TsirkinMay 4, 2007
  11. Yann DirsonMay 4, 2007
  12. Yann DirsonMay 4, 2007

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.