Re: What's cooking in git.git (Sep 2025, #02; Wed, 3)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> Le 4 sept. 2025 à 12:21, Junio C Hamano <gitster@xxxxxxxxx> a écrit :
> 
> "Kristoffer Haugsbakk" <kristofferhaugsbakk@xxxxxxxxxxxx> writes:
> 
>> • Incorporate Peff’s patch[2] if I’m up to the task
>> • Then mention on the whatchanged *hint* that they can make an alias to
>>  shadow it
> 
> Hmph, I am not sure if training users that they can always alias
> anything away in order to keep deprecated names forever is a good
> idea overall.  That way, we will ensure that newer users when
> watching over shoulders of more old timers will have more chance to
> get confused by unusual synonyms old timers would use without any

They stand an equal chance to be confused by my unusual aliases and scripts :p

> advantage over the more modern ways they have learned at school,
> other than the "mustle memory" of old timers.

(Most of which I try to update to take account for modern Git CLI practice.)

> But if nobody is disturbed by that idea, then the above two would be
> a reasonable way forward.

Agreed. I suppose the question is how quickly the changes should land and release: were you planning on trying to get these messages out as a fast .1 or similar to help quell the noise more quickly? Or wait a while for the next normal release, in which case baking a few more patches on top seems logical?




[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux