On Mon, 17 Mar 2014 14:50:56 +0100, Stephan Beal <sgb...@googlemail.com>
wrote:
On Mon, Mar 17, 2014 at 2:40 PM, j. van den hoff
<veedeeh...@googlemail.com>wrote:
personally, I think it is great, that checkin comments _can_ be edited
after the fact (contrary to some other DVCSes) --
Just to avoid any confusion from those who don't know the difference: in
Fossil you can't actually edit anything at all once it's been committed.
You can _amend_ the record with the new data, but not change the
original.
e.g. a new commit comment is actually just a tag named "comment", and the
system takes the most recent comment tag which was applied to that
artifact. This provides the illusion of some data having been edited,
when
in fact none has been changed.
I was imprecise, sorry. and it's of course the same as if you "edit" some
document content. so, in the repo it _is_ "append only" (if one wants to
call it that) but the "illusion" that the original checkin comment has
changed (as far as the user is concerned it really has, apparently) serves
well to get a timeline with clean checkin messages (one of them being that
another checkin comment has been edited, I believe?).
in any case, something like that would be rather desirable for the
ticketing system as well in my view.
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
