Hi Andy, On 5 March 2015 at 12:23, Andy Goth <andrew.m.g...@gmail.com> wrote: > I added a few suggestions to the Fossil 2.0 wiki page > > https://www.fossil-scm.org/index.html/wiki?name=Fossil+2.0 > > without discussing them on the mailing list. Probably a bad idea, sorry > about that. So I'm drawing everyone's attention to it. > > The ideas I've posted are: > > ### 1. Show cherrypick and backout merges in timeline and context. > > Differentiate between normal, cherrypick, and backout merges by the shape of > the arrowhead. > > ⭕: Cherrypick merge (resembles a cherry) > ❌: Backout merge (signifies removal)
FWIW, these are tiny, faint boxes in google chrome. It doesn't resemble anything, especially a cherry. Perhaps on your browser it's fine, though. I've attached a screenshot of the wiki page. > > ### 2. Require directory name argument to open command. > > One thing that repeatedly surprised me when learning Fossil was that the open > command opens the repository into the current working directory. This left me > either confused at there being no apparent effect (except a hidden file > called .fslckout, in the case of a new repository) or angry about Fossil > making a big mess in my current directory (not easily undone because close > doesn't delete). > > I would have picked up on this behavior instantly had the open command > required the directory name as an argument following the repository argument. > The directory would be created if it doesn't already exist. For example: > > fossil new repo.fossil > fossil open repo.fossil repo > cd repo Yes, this is great! Most fossil people have a fossil specific directory to house all projects and inside that directory you'll have *.fossil repos and those directories, so it makes sense to include a command to mkdir when opening. > This definitely hoses every script that calls open, but that's intentional > since the goal is to force the (inexperienced) user to confirm that he really > wants to open into the current directory. For current Fossil, a compromise > form could be implemented which defaults the directory to ".", but Fossil 2.0 > would remove the default. > Yes, the uninitiated will learn it faster than fossil experts, but that's okay--we'll just have to document it well. > - -- > Andy Goth | <andrew.m.goth/at/gmail/dot/com> -- ------- inum: 883510009027723 sip: jungleboo...@sip2sip.info xmpp: jungle-boo...@jit.si
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
