On Mon, Oct 27, 2014 at 1:18 PM, Tony Papadimitriou <to...@acm.org> wrote:
> I guess the same scenario would be valid if one used a server but had > private branches. My understanding is that private branches do not sync so > the only way to move to another location is to move the whole fossil file. > Correct? > That's my understanding - that private artifacts do not sync until they are made non-private (by pushing them). That said, i've never used private branches in fossil - i'm working from my memory of the source code. You can eventually publish private branches, making them public, but i can't tell you off-hand how to do it. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
