"For those who don't know about it: fossil supports a -M (big emm) option which reads the commit message from a file and doesn't not apply any #-related special handling to the content (or it didn't at the time it was implemented, and i'm assuming that hasn't changed)" ----- stephan beal Whoa, I didn't know that? If this is true, why couldn't fossil collapse that same effect for a manual commit step? My commit use model is I always select all and delete all predefined comments and paste in my own. Unless I am doing a merge and then I take advantage of the autogenerated sha1 artifact specified. But, then I have to remember to delete the dang '#' symbol!! :(
It is more work to specify a message file, since my history/commit documents are appended and not isolated or new per commit. On Thu, Oct 17, 2013 at 10:23 AM, <[email protected]> wrote: > I also take exception to this being only a recent phenomena. I have been > burned several times now, but as you say, this is not a mission critical > error. > However, me and my users cherish the timeline view and are confused by > random omissions of '#'this or '#'that. So I do not feel the comments are > trivial. > > I would really appreciate any of the other suggestions. > Multi-char lead being less onerous. > > #Thanks for fossil! > > > On Thu, Oct 17, 2013 at 10:03 AM, j. van den hoff < > [email protected]> wrote: > >> On Thu, 17 Oct 2013 15:59:45 +0200, Stephan Beal <[email protected]> >> wrote: >> >> On Thu, Oct 17, 2013 at 3:55 PM, j. van den hoff >>> <[email protected]>**wrote: >>> >>> `FOSSIL:' or even `FOS:' as the unique identifier (which mostly is what >>>> somebody else already proposed). I'd say that will work better than `#' >>>> (i.e. accidentally names clash very very unlikely) and sufficiently >>>> stands >>>> out on the respective lines due to the capitalization. >>>> >>> >>> >>> Historical note (i don't think you've been on the list long enough to >>> have >>> seen this): here's the summary from some code comments in fossil: >>> >>> /* >>> ** Locate the root directory of the local repository tree. The root >>> ** directory is found by searching for a file named "_FOSSIL_" or >>> ".fslckout" >>> ** that contains a valid repository database. >>> ** >>> ** For legacy, also look for ".fos". The use of ".fos" is deprecated >>> ** since "fos" has negative connotations in Hungarian, we are told. >>> ... >>> >>> A user made us aware at some point that fos is an ugly/inappropriate word >>> in his language (i concur with the code comment that it was Hungarian). >>> >> >> well, there are _towns_ having offending names >> >> http://en.wikipedia.org/wiki/**Fucking,_Austria<http://en.wikipedia.org/wiki/Fucking,_Austria>:-) >> >> so I presume the hungarian users will probably don't take real offense >> but anyway "FOSSIL:" would be fine to. >> >> >> >>> >> >> -- >> Using Opera's revolutionary email client: http://www.opera.com/mail/ >> ______________________________**_________________ >> fossil-users mailing list >> [email protected].**org <[email protected]> >> http://lists.fossil-scm.org:**8080/cgi-bin/mailman/listinfo/** >> fossil-users<http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users> >> > >
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
