From: Felipe Contreras <felipe.contreras@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jeff King <peff@peff.net>,
git@vger.kernel.org, Sverre Rabbelier <srabbelier@gmail.com>,
Thomas Rast <trast@student.ethz.ch>
Subject: Re: [PATCH 1/2] transport-helper: report errors properly
Date: Thu, 11 Apr 2013 16:35:00 -0500 [thread overview]
Message-ID: <CAMP44s1EJO3gMyb-SCGL3mWQOgsgYDb87e2mx3spO=V71hs+=g@mail.gmail.com> (raw)
In-Reply-To: <7vbo9kj41y.fsf@alter.siamese.dyndns.org>
On Thu, Apr 11, 2013 at 1:49 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Felipe Contreras <felipe.contreras@gmail.com> writes:
>
>> On Thu, Apr 11, 2013 at 11:59 AM, Jeff King <peff@peff.net> wrote:
>>
>>> But I give up on you. I find most of your commit messages lacking in
>>> details and motivation, making assumptions that the reader is as
>>> familiar with the code when reading the commit as you are when you wrote
>>> it. I tried to help by suggesting in review that you elaborate. That
>>> didn't work. So I tried to help by writing the text myself. But clearly
>>> I am not going to convince you that it is valuable, even if it requires
>>> no work at all from you, so I have nothing else to say on the matter.
>>
>> Me neither. I picked your solution, but that's not enough, you
>> *always* want me to do EXACTLY what you want, and never argue back.
>>
>> It's not going to happen. There's nothing wrong with disagreeing.
>
> Heh, it seems that I was late for the party.
>
> Writing only minimally sufficient in the log messages is fine for
> your own project. We won't decide nor dictate the policy for your
> project for you.
>
> But _this_ project wants its log messages to be understandable by
> people who you may disagree with and who may have shorter memory
> span than you do.
Having a shorter memory span is irrelevant when you are _never_ going
to go back and ask the question the commit message is answering. And
if it indeed is an important question, the answer belongs in the code
comments.
> Disagreeing with that policy is fine. You need
> to learn to disagree but accept to be part of the project.
Yeah, I accept that you will commit whatever you want, but I still
don't think this verbosity serves the purpose you think it serves.
Some one-liners deserve pages of commit messages, but this one is not
one of them. People are easily deceived, and because you saw one
commit message that needed more information, you think all of them do,
but no, some don't don't, and this is one of them. It's not serving
any real purpose.
--
Felipe Contreras
next prev parent reply other threads:[~2013-04-11 21:35 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 14:40 [PATCH v4] transport-helper: report errors properly Felipe Contreras
2013-04-08 18:20 ` Sverre Rabbelier
2013-04-08 19:30 ` Jeff King
2013-04-08 19:28 ` Jeff King
2013-04-09 21:38 ` Thomas Rast
2013-04-09 21:50 ` Jeff King
2013-04-10 21:13 ` [PATCH v5 0/2] reporting transport helper errors Jeff King
2013-04-10 21:15 ` [PATCH 1/2] transport-helper: report errors properly Jeff King
2013-04-10 21:22 ` Sverre Rabbelier
2013-04-10 21:46 ` Eric Sunshine
2013-04-11 13:22 ` Felipe Contreras
2013-04-11 16:18 ` Jeff King
2013-04-11 16:49 ` Felipe Contreras
2013-04-11 16:59 ` Jeff King
2013-04-11 17:57 ` Felipe Contreras
2013-04-11 18:49 ` Junio C Hamano
2013-04-11 21:35 ` Felipe Contreras [this message]
2013-04-11 18:44 ` Junio C Hamano
2013-04-11 21:21 ` Felipe Contreras
2013-04-11 23:05 ` Junio C Hamano
2013-04-13 5:42 ` Felipe Contreras
2013-04-13 6:00 ` Jeff King
2013-04-13 6:43 ` Felipe Contreras
2013-04-14 5:23 ` Junio C Hamano
2013-04-14 15:54 ` Felipe Contreras
2013-04-10 21:16 ` [PATCH 2/2] transport-helper: mention helper name when it dies Jeff King
2013-04-10 21:23 ` Sverre Rabbelier
2013-04-10 21:28 ` Jeff King
2013-04-10 21:35 ` Sverre Rabbelier
2013-04-10 23:13 ` [PATCH v4] transport-helper: report errors properly rh
2013-04-11 3:39 ` Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMP44s1EJO3gMyb-SCGL3mWQOgsgYDb87e2mx3spO=V71hs+=g@mail.gmail.com' \
--to=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=srabbelier@gmail.com \
--cc=trast@student.ethz.ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).