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 - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html