On 2007-11-20 09:53:55 -0500, Jon Smirl wrote:
> What about storing each stg git patch in a branch and then
> auto-merging them into the working copy?
You mean making a "patch" be a topic branch rather than just one
commit, with the successive commits on the topic branch reflecting the
changes to the patch over time?
How would you handle operations such as refreshing a non-topmost
patch, reordering patches, dropping patches, etc? It seems to me that
the operation you'd want then would look more like cherry-picking than
merging, at least sometimes.
It might work, but someone would have to sit down with pen and paper
and work out how all the common operations should work.
--
Karl Hasselström, kha@xxxxxxxxxxx
www.treskal.com/kalle
-
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
