On 9/11/2015 7:11 AM, Richard Hipp wrote:
On 9/11/15, Stephan Beal <sgb...@googlemail.com> wrote:
On Fri, Sep 11, 2015 at 1:22 PM, Richard Hipp <d...@sqlite.org> wrote:
I'm not sure "--undo" is the right name for this option. Other
suggestions?
--from-undo
or:
--from undo (special-case name)
....
Adding support for "undo" as a special-case name of "--from" seems
problematic since that would make it harder to do a diff against a
branch named "undo".
I like the special case named "undo". It fits neatly alongside "tip",
"current", "next", "previous", "prev", and "ckout". Like all the other
specials except "tip", it probably only has meaning if fossil is running
in an open checkout.
There is already a mechanism to distinguish a branch (or tag) that
matches a special name or hash. You would say "tag:current" to talk
about the branch named "current", or "root:current" to name the checkin
the branch is rooted on. So "tag:undo" would name the branch, as would
plain "undo" if there is no current checkout.
This is documented here:
http://fossil-scm.org/xfer/doc/trunk/www/checkin_names.wiki
but perhaps deserves some additional visibility somehow.
I guess the other question to ask is how many of us have a project with
a branch named "undo"?
It appears that as of just now, there is no branch named undo in fossil
itself. For the record, I don't recall ever using undo as a branch name
in any of my personal repositories.
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp. http://www.CheshireEng.com/
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
