On Dec 9, 2009, at 12:39 PM, Jeremy Cowgar wrote: > In the 3 features... thread, I read from Michael: > > " 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'). " > > It seems that fossil is in need of two things: > > 1. Save the commit message to a file when the commit failed > 2. Provide a means of making fossil read the commit message from a > file
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. 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.e. > > $ fossil commit > (enter your message in the editor that was loaded) > ... ERROR ... > ... Your commit message was saved to fossil-commit.a493bd8 ... > $ # fix error > $ fossil commit -cf fossil-commit.a493bd8 > ... SUCCESS ... > > This would also make it easier to integrate into various editors/ > IDEs, i.e. being able to ask a commit message, save it to a file > then call the appropriate fossil command. > > Jeremy > > _______________________________________________ > fossil-users mailing list > [email protected] > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users D. Richard Hipp [email protected] _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
