On Feb 10, 2005, at 6:41 AM, Max Bowsher wrote:
> Adrian Robert wrote:
>>> ------- Additional comments from firstname.lastname@example.org Fri Jan 28 12:46:41
>>> -0800 2005 -------
>>> It could be done, yes. But, if we had an issue for every "it would be
>>> nice if
>>> ...", the issue tracker would be so bloated that we'd never find
>>> anything useful
>>> in it. If someone wants this, then they need to discuss it on the
>>> list, and
>>> be prepared to write patches.
>> OK, thanks for at least taking a look at it. Although I phrased the
>> RFE as "it would be nice", I think the priority of it ought to be
>> relatively high since it is an existing CVS feature and an extremely
>> useful one at that.
> What do you find it useful for? It's not clear to me (or many others
> here) what it is useful for, other than statistics for statistics
It's a quick way to determine the rough magnitude of changes that went
into a certain revision. This is useful in general for finding out the
amount of work/change has gone into a file over various periods of time
(helps you identify where extension / maintenance work is being focused
in a project, can suggest places to refactor, etc.). It also helps in
particular when you are trying to isolate a bug that popped up and want
to quickly determine which of a set of changed files in the date range
the bug emerged it would pay to examine first. It's a good utility as
well for detecting "botched commits", where a previous change was
undone, code was accidentally deleted and/or mis-pasted, etc..
At a more abstract level, the point of having logs is to provide a
higher-level overview of the changes in a repository than detailed
diffs. The +/- line number count supports this, in a complementary way
to the verbal log messages.
As for my other comments, I apologize for expressing my frustration in
an "unproductive" tone. Probably I am misinformed, through my own
negligence, on a number of points. Thanks for the suggestion of
writing a commit script, I'll look into it if I find the time.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Thu Feb 10 18:00:48 2005