On Wed, Jul 3, 2013 at 2:50 PM, Richard Hipp <d...@sqlite.org> wrote:
> > > On Wed, Jul 3, 2013 at 5:42 PM, Matt Welland <estifo...@gmail.com> wrote: > >> >> I still feel that ideally "fossil gdiff" should not tie up the database >> and prevent commits but I understand that may not be easy to fix. However >> adding the full file name of the actual locked database to the error >> message would help a lot. >> >> > I agree, "fossil gdiff" should not keep the database locked. FWIW, the > "fossil diff --tk" command does not keep the database locked, at least not > that I have noticed. If "fossil gdiff" is locking the database, probably > the reason it has not been fixed is that I never used "gdiff" myself and so > have not noticed the problem. > "fossil diff --tk" exits instantly with exit code 0 on my system. Is there setup necessary to use this? I dug though the help and mailing list and didn't run across any details. I'm using fossil version 1.25. Thanks > -- > D. Richard Hipp > d...@sqlite.org > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > > -- Matt -=- 90% of the nations wealth is held by 2% of the people. Bummer to be in the majority...
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
