On Fri, 10 Feb 2012 15:35:13 +0100 frantisek holop <min...@obiit.org> wrote:
> > > I think it should be fixed to a better behaviour (the command to > > > emit an error > > > and not overwrite the file). > > > > > > > i've patched this locally to do: > > > > [stephan@hamsun:~/cvs/fossil/fossil]$ ./fossil artifact abcdcafe > > ./fossil: Could not resolve artifact name/ID. > > how about: > > $ ./fossil artifact abcdcafe > ./fossil: abcdcafe: no such artifact Sorry for another bikeshedding plug, but if we recall how perror() works, a more Unix-way approach to error reporting whould be reverse the static and varying parts, so that the error message becomes: no such artifact: abcdcafe _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
