Re: [PATCH v3] build: add default aliases

[John Szakmeister <john@szakmeister.net>]

On Tue, Sep 24, 2013 at 10:35 AM, Felipe Contreras
<felipe.contreras@gmail.com> wrote:
> On Tue, Sep 24, 2013 at 6:06 AM, John Szakmeister <john@szakmeister.net> wrote:
[snip]
>> There's nothing objective about "Nobody every (sic) agrees changes are
>> good".  If it were true, no changes would get in.
>
> It is true, where by "changes" I mean "changes from common user's
> point of view", actually, a tiny amount of then do sneak in, so let me
> be precise: "Virtually nobody ever agrees important changes from the
> common user's point of view are good".
>
> So now that I'm being clear, do tell, name one important change in Git
> from the user's point of view that happened in the last two years.

Credential helpers.

>> Also, you don't know that any of those changes would benefit "99% of
>> all users".  It's a guess or an estimate but it's not based on
>> anything concrete.  It might be a good guess--and in this case, I
>> think it is--but it's not a concrete fact.  Don't make it sound like
>> it is.
>
> Sure, it's not a concrete fact, but the actual probability most likely
> follows a beta distribution with alpha=15 and beta=1. Is that more
> precise for you?

It's not about precision, it's that you don't have any actual facts to
stand on but you speak like you do.  Then when someone questions it,
you accuse them of being against fixes for the user.  I wish you'd
stop it and do something more constructive to help move things along.

>>> If you don't agree my comment is accurate, that's one thing, but
>>> labeling it as an attack is another.
>>
>> Don't turn it around.  A number of your patches and emails poke at the
>> community of the Git project and you know it.  It's simply not helping
>> the situation.
>
> Show me a patch that "pokes" at the community. All my patches have
> technical descriptions, and help improve Git.

You're filtering what I said again.  Take a look at the first message
is this thread.

I'll agree the patches themselves have been free of this, but the
cover letters--which I consider to be part of the patch--and ensuing
conversation has not.  If you need another example, look at the cover
letter for your transport helper patches.

None of this is news to you.

[snip]
>>> I would admit I was wrong if an /etc/gitconfig is indeed shipped by
>>> default, and agree that the Git project is indeed welcome to change,
>>> but that's not going to happen.
>>
>> And there it is again.  Predicting the future now?  Objectively and
>> accurately?  Please stop.
>
> Yes I am. Feel free to go back to this mail and tell me I was wrong
> when they do what I said they won't.

I have no need for that, and I'm done talking to you about any of this.

-John