On Sat, Feb 25, 2012 at 01:33:45PM -0500, Leo Razoumov wrote:
> Hi List,
> I am trying to accomplish a cascading work-flow Personal.fossil ->
> Team.fossil -> Public.fossil without history rewriting.
> 
> I would like to entertain an idea of adding explicit "public" tag
> which will propagate in a way similar to "private" tag behavior.
> Push/Pull behavior will be modified to accomplish the following

I might rather like to see the ability to specify which private branches
get pushed and which don't. For example, using the --private option
would default to all private branches, but add an additional argument
that would either (or both) specify which branch(es) to push and which
branch(es) to not push.

-- 
Christopher Berardi
http://www.natoufa.com/

May grace and peace by yours in abundance.
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to