I like the B cases... in fact I'd indent the details a bit so that the
comments are easier to find visually.

On 24 November 2017 at 11:53, <[email protected]> wrote:

> I understand the need for links, but do users really need truncated hashes
> for every line?
> Can the link be applied more subtly?
> Can there be a similar "quiet" setting for the Timeline like *Per-Item
> Time Format = (off) *to conserve space?
> My commits prepend a simple timestamp in the comment and multiline text
> for more immediate descriptions right up front.
> Having this tail every entry -> (check-in: [4dfa592f]
> <https://www.fossil-scm.org/b/info/4dfa592f27f88e82> user: drh
> <https://www.fossil-scm.org/b/timeline?u=drh&c=2017-11-16+02%3A43%3A49&nd&n=200>
>  tags: trunk
> <https://www.fossil-scm.org/b/timeline?r=trunk&nd&c=2017-11-16+02%3A43%3A49&n=200>)
> <-
> makes the timeline quite busy.
>
> Thanks for Fossil!
>
> On Fri, Nov 24, 2017 at 11:27 AM, Richard Hipp <[email protected]> wrote:
>
>> On 11/24/17, bch <[email protected]> wrote:
>> >>
>> >>   (1)  The "details" section is shown on a separate line below the
>> >> check-in comment.
>> >>   (2)  The "details" are in the same font-color as the comment-text
>> >> but have a slightly reduced font size.
>> >>
>> >
>> > I don’t see that reflected on the link.
>>
>> Those are CSS changes.  So you will need to press "Reload" in your
>> browser, possibly multiple times if you use Chrome, before you will be
>> able to see the changes.
>>
>> --
>> D. Richard Hipp
>> [email protected]
>> _______________________________________________
>> fossil-users mailing list
>> [email protected]
>> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>>
>
>
> _______________________________________________
> fossil-users mailing list
> [email protected]
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
>
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to