Cc: Josef Sipek <jsipek@...>, Michael S. Tsirkin <mst@...>, Junio C Hamano <junkio@...>, Catalin Marinas <catalin.marinas@...>, <git@...>, Josef 'Jeff' Sipek <jsipek@...>
On Wed, Apr 25, 2007 at 11:37:05PM +0200, Robin Rosenberg wrote:
You are right, in that what can be done with such branches is limited.
BUT you can safely "stg branch --create" off any remote stgit stack.
Then you can "stg rebase origin/master" to port your stack to the new
tip of the remote stack.
The next stgit release will allow you to declare the pull-policy for
your stack as "rebase", so when you "stg pull" it will indeed rebase
to the new tip of the parent branch.
As for publishing, I use the following config entries to publish my
own stack of patches to stgit. You can see at
http://repo.or.cz/w/stgit/ydirson.git that gitweb shows pretty clearly
the structure of the stack (even though things could surely be made
better).
I use "git push -f" to publish - maybe the "+" refspec syntax would
work with push, I'll try it next time :)
[remote "orcz"]
url = git+ssh://ydirson@repo.or.cz/srv/git/stgit/ydirson.git
push = refs/heads/master:refs/heads/master
push = refs/patches/master/*:refs/patches/master/*
Maybe we should provide some degree of automation in stgit itself
(eg. "stg branch --publish" or something).
Hope this helps,
--
Yann.
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html