On 2012-08-25 09:47, Scott Robison wrote:
I downloaded the lastest Windows fossil build tonight and am giving
DVCS another shot. Some notes:
1. I like the fact that I could --date-override the initial create
date stamp.
1a. I wish that I could --date-override a commit at the command line
so that I didn't have to edit the date stamp via the web interface
later.
1b. If you don't type the date stamp format just right, fossil will
crash trying to display the time line in the web interface. In my
case
I typed "8:12:23" instead of "08:12:23" for the edited time, omitting
the leading 0.
2. I am color blind. The color coding of bullet points in the "Edit
User" pages explaining which marks indicate what is practically
worthless to me (I spent a while staring at them trying to figure out
what the difference was; I'm not complaining, it's just my burden,
and
I'm fortunately to not have worse burdens, really). I mention this
only as a usability issue for someone to consider. I really don't
know
what would be better, and hate to be one of those people that sounds
like "accommodate my disability even though it works for most people
just fine!" Some obvious alternatives that pop into my head are to
use
multiple bullet shapes instead of just color coding the same shape or
to use subscript or superscript digits or some such.
3. I would be happy to take a stab at modifying the source to
implement the stuff above, and I understand there is some sort of
copyright assignment or waiver form to be filled out... If someone
could forward that my way I would appreciate it.
SDR
There is a non documented option to commit to override date and user
--date-override
--user-override
Why do you want to override the date? Are you converting a repository?
What the colour coding does is, in de case of multiple branches,
is that a commit square gets the same colour as the comment
The left side is always the trunk. E.g.
[ ] These are on the trunk and has no colour
|
|
| [g] This text has the colour green
| |
| |
| |
| [p] This text has the colour purple
It is helpful aid to see on which branch activity is going on. But you
can get that information also by
looking at the squares.
Maybe we could number or symbolise the branches in addition to the
colouring like
2012-08-24 |
14:50 | [2] 2 [b4ea94b488] Leaf: merge unicode branch
(user: jan.nijtmans, tags: eclipse-project)
| /|
| / |
| / |
| / |
13:42 | [3] | 3 [c780793749] Leaf: add mkdir to the
unicode-supported functions add chinese-named file and
| | | directory in test directory, demonstrating
the fix (user: jan.nijtmans, tags: unicode)
| | |
13:15 | [3] | 3 [d8e1431fc0] Better support for unicode
filenames on Win32 (Not tested on
| | | other platforms yet, will not work!) (user:
jan.nijtmans, tags: unicode)
| | |
| / |
| / |
|/ |
08:16 +-------[2] 2 [abbc00fc5b] Merge in the mingw build
enhancements (user: jan.nijtmans,
| | tags: eclipse-project)
08:13 [1] | 1 [4e93e84e55] wiki tweaks regarding MinGW
build enhancements
| |
| |
05:56 [1] | 1 [02bff595e1] One more minor Win32
| |
2012-08-23 | |
I'm not sure if that would be of real value to you?
--
Rene
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
