Re: [git-for-windows] Re: [ANNOUNCE] Git for Windows 2.9.3

[Michael J Gruber <git@drmicha.warpmail.net>]

Johannes Schindelin venit, vidit, dixit 23.08.2016 15:54:
> Hi Duy,
> 
> On Mon, 22 Aug 2016, Duy Nguyen wrote:
> 
>> On Thu, Aug 18, 2016 at 3:37 PM, Johannes Schindelin
>> <Johannes.Schindelin@gmx.de> wrote:
>>> Hi Junio,
>>>
>>> On Wed, 17 Aug 2016, Junio C Hamano wrote:
>>>
>>>> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>>>>
>>>>>> And then your "git cat-file" patch can be upstreamed with the option
>>>>>> renamed to (or with an additional synonym) "--filters", which would make
>>>>>> things consistent.
>>>>>
>>>>> Right. I would like to ask for a `--smudge` synonym nevertheless, just
>>>>> because I already use this. On the other hand, it is early enough to tell
>>>>> everybody who knows about this feature to change their invocation (anybody
>>>>> who would know about `--smudge` would be in that 1% of users that have
>>>>> read the release notes, so most likely would read the next release notes,
>>>>> too).
>>>>
>>>> It is OK if it were your private edition, but you end up hurting
>>>> your users if you need to redo the feature differently.
>>>
>>> Unfortunately, this is the situation of Git for Windows from its
>>> beginning: there has not been a single time that Git for Windows could
>>> live with unpatched upstream Git's source code.
>>>
>>> Business as usual, though.
>>
>> Bug fixes is one thing, features is completely different.
> 
> Oh? Completely?
> 
> So the core.hideDotFiles feature should have forced me to rename Git for
> Windows to, say, DschoGit on Windows?
> 
> Let's just stop here. This is getting too silly.

I see more truth than silliness in Duy's suggestion. Maybe you want to
re-read what you wrote to trigger his response, and consider adjusting
your attitude ("I want this now so I'll release it in Git4Win") rather
than the downstream name.

Michael