On Mon, Oct 27, 2014 at 11:58 AM, Tony Papadimitriou <to...@acm.org> wrote:
> /somepath/a.fossil > /otherpath/b.fossil (OPEN) > That won't (or shouldn't) work because once a repo is closed it will (or should) no longer show up in the 'all' list. > And, how about a command to close all open repos at once, e.g., at the end > of the day? FOSSIL ALL CLOSE should of course stop at the first repo that > has, say uncommitted changes, the same way a FOSSIL CLOSE does, unless a > –FORCE option is used. > 'close' is a very rarely used feature - i'd be really surprised if there's a good use case for adding support for it to 'all'. Since i've been using fossil (Christmas of 2007) i've used 'close' maybe... 5 times? Regarding stopping at the first repo which has uncommitted changes: the 'all' command doesn't have enough info to know the reason a certain 'close' fails - it basically runs a loop which looks like: for i in $(list of all opened repos); do fossil _some_operation_ $i || exit $? # this runs in a separate process done It can of course stop at the first error, but cannot tell you, "we're stopping because one of the repos has uncommitted changes." Can you tell us how you are using 'close' - i strongly suspect you don't really need it for what you are doing. There is very, very rarely a true requirement need to "close" a repo. -- ----- 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
