On Dec 9, 2009, at 1:29 PM, D. Richard Hipp wrote:
>
> 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?
What's bitten me a time or two is saying "fossil commit", seeing
the list of files, and then saying, "Oh, rats, I forgot to do a
fossil add", or "I forgot to update a doc file". So I do it;
and then fossil tells me that the checksum has changed (or something
like that) and doesn't commit. This case comes up often enough
that it would be nice if fossil allowed it to work, possibly with
a confirmation from the user.
------------------------------------------------------------------
will -at- wjduquette.com | Catch our weblog,
http://foothills.wjduquette.com/blog | The View from the Foothills
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
