On 08/07/2013 07:50 PM, Junio C Hamano wrote:
> Stefan Beller <stefanbel...@googlemail.com> writes:
>> I'd deprecate it first for a year or such and remove it then.
>> In the meantime we could implement already remove the code
>> and change it to:
>> + int cmd_whatchanged(int argc, const char **argv, const char *prefix)
>> + {
>> +    return cmd_log(argc, argv, prefix)
>> + }
>> Also we should make sure everything git whatchanged can do,
>> can easily be done with git log <options>.
> That's even worse than "deprecating".
> Your first step already changes the behaviour for people who really
> use the command, without telling them _why_ the behaviour has
> suddenly changed at all, while not helping *ANYBODY*.
> The only thing it does is to scratch an irrelevant itch by people
> who peek the codebase and find an old command whose existence does
> not even hurt them.  They may have too much time on their hand, but
> that is not an excuse to waste other people's time by adding extra
> makework on our plate, or changing the behaviour for people who use
> the command without explanation.
> Feeling irritated somewhat...

Well if we make sure the whatchanged command can easily be reproduced
with the log command, we could add the missing parameters to it, hence
no change for the user. (git whatchanged == git log --raw --no-merges or
git log --wc [to be done yet]).

So I did not mean to introduce a change for users!

But in general I like the idea to *remove* lines of code.


Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to