Re: Ensimag students projects, version 2013

Jeff King [off-list ref] writes:

FWIW, I do not think it was so much rejected as that I had initially
planned to implement it, then decided against it. Mostly because I
wanted to actually get annoyed with each piece of advice before
disabling it. Because sometimes the right answer is actually "make the
advice better".

I am pretty much aligned with this position. "Make the advice
better" not only refers to what we say (i.e. the message) but when
we say it, and keeping the advice variables enabled is the only way
to notice when we are being excessive.

I'd hate to see any Git developers running with advice turned off
for this exact reason.

Junio C Hamano wrote:

I'd hate to see any Git developers running with advice turned off
for this exact reason.

Improving advice is your itch, but it is certainly not my itch.  I
don't want to see messages like "Commit your changes or stash them",
or "try --continue | --skip | --abort" cluttering up my valuable
terminal output when I know what to do.  I don't care how they can be
made "better", because I don't want to see them in the first place.

You should have nothing against me for running with all advice turned
off.  It's not your job to dictate how a software should be used, but
rather design it so that intended usage is the most intuitive.