On Mon, Oct 7, 2013 at 6:38 AM, Richard Hipp <d...@sqlite.org> wrote:
> On Mon, Oct 7, 2013 at 9:12 AM, Stefan Bellon <sbel...@sbellon.de> wrote:
>> But more severely, the information
>> who changed the line is now not present anymore at all.
>
>
> Most people are more interested in the fact that the line changed.  The
> identity of the editor is of secondary importance,

Not when you have tracked a bug to a specific line, or set of lines
(without having bisected (*) or some such) and now want to know with
whom to talk about these lines regarding intent, etc.


(*) With bisect we have the change, and this know who made it. However
sometimes it is possible to determine a problematic line without
having bisected during investigation, and then we do not directly know
the relevant person. That is to me the main importance of "annotate"
then.

> and can be found by one
> additional click in the rare case where it actually matters.

Ah. This click however works only in the web interface.
Stefan seems to look at the output of "fossil annotate', which is the cli.
There this becomes "one more command" to retrieve the info about the
change shown, and that is more inconvenient than a single-click.
Assuming that this information is actually available to the command
line (**).

And while I can also see that "single command" more may not be that
much in the context of a script processing the output of annotate, it
does generate more complexity in the script, like:
- cache which changes we have pulled the user info for already, as a
file will have many more lines than relevant changes
- more parsing needed to get the user information out of the change.

(**) Ok, in the extreme case we can 'wget .../raw?name=UUID' and then
pull the information out of the raw manifest we get this way.

>  The username
> was therefore removed from the primary display in order to reduce the amount
> of clutter and to make the output easier for humans to read.
>
> We will take your email as a feature request to add the username back in as
> a run-time option.



-- 
Andreas Kupries
Senior Tcl Developer
Code to Cloud: Smarter, Safer, Fasterâ„¢
F: 778.786.1133
andre...@activestate.com
http://www.activestate.com
Learn about Stackato for Private PaaS: http://www.activestate.com/stackato

Tcl'2013, Sep 23-27, New Orleans, LA, USA @ http://www.tcl.tk/community/tcl2013/
EuroTcl'2013, July 6-7, Munich, GER
_______________________________________________
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