-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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.

    ▲: Normal merge (or ◀ or ▶ as appropriate)
    ⭕: Cherrypick merge (resembles a cherry)
    ❌: Backout merge (signifies removal)

The merge lines may also be shown in different colors, e.g. green for 
cherrypick and red for backout.

Suggest allowing this feature to be configurable via theme. Also may be a user 
checkbox to show or hide cherrypick/backout merges.

### 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

Opening into the current directory could still be done by supplying "." as the 
directory name.

fossil new repo.fossil
cd repo
fossil open ../repo.fossil .

This change would resemble the behavior of the fusefs command which requires a 
directory name argument.

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.

- -- 
Andy Goth | <andrew.m.goth/at/gmail/dot/com>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBAgAGBQJU+LtPAAoJELtYwrrr47Y4J7oIAMbNIOi5f9LqkOGbaINlSmrl
MNs1iFkbOYvJw05j73MrjCNIxfrvqK3qnssvUhXvStLW8X6/r8Bz8IVzgYA4Xs/R
+QgVYVG5sKw9yqhwqAfOZWw8F9eKzVgk02IymHVBQ4WwZT5/tp+ug9loOEcw6zqb
Vs00eXrBBqGNWKapAFxW7vgBRNuhX/uy75MH0cZnfVEo/cCjkgiKagUXlW6vMoKp
eJAdErU2JuSV5phiG5eAThvnRGeq6OuoBlCf0OcosYvZP/YahxyahUxqBK+Li5Wk
O+V98xSfVouyPPYQ2Hjv2LXCpP4uo0dSmjn+1QljE3t5FbSDlO0EeGRUkqo1U90=
=QJgu
-----END PGP SIGNATURE-----
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to