"D. Richard Hipp" <[email protected]> wrote: > > It seems to me that a better approach would be to improve the "commit" > command so that it does a better job of detecting problems *before* it > asks you to type in the commit message. In other words, if the commit > is going to fail, have it fail early. >
Yes, that does make sense, but I believe the suggested functionality still has merit, especiallt for being able to script/integrate fossil into other products easily. i.e. reading a commit message from a file instead of on the command line. > What is it that is causing your commits to fail so frequently? What > can we do to get fossil to detect these problems before you type in > your commit message? > I'm not so sure that I have had commit's fail frequently. It has happened to me but I can't remember why. I was simply providing possible solutions to fix the retyping issue of the original author. I did spawn this thread from the 3 features request thread. Michael wrote: " Secondly, I always get bit with my commit failing and then having to type in my comment again (after the monkeying around with 'fossil rm'). " in: http://www.mail-archive.com/[email protected]/msg01012.html Jeremy _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
