From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: Ramsay Jones <ramsay@ramsayjones.plus.com>,
Jeff King <peff@peff.net>, GIT Mailing-list <git@vger.kernel.org>
Subject: Re: [PATCH v2] archive-tar: fix a sparse 'constant too large' warning
Date: Wed, 10 May 2017 12:55:25 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1.1705101254440.146734@virtualbox> (raw)
In-Reply-To: <xmqqr2zxzjf9.fsf@gitster.mtv.corp.google.com>
Hi Junio,
On Wed, 10 May 2017, Junio C Hamano wrote:
> Ramsay Jones <ramsay@ramsayjones.plus.com> writes:
>
> > Yeah, I had a similar comment in the commit message (but much more
> > verbose than your concise addition above), but I edited it several
> > times, without finding a wording that I liked. I eventually removed
> > it, because it didn't really add any value. :(
>
> I tend to agree that the proposed additional comment does not add much
> value. It assures the readers that we (at the time of applying this
> patch) know that the earlier use of ULL was not done with a good reason
> but was merely an accident, and strengthens the claim that this is a
> good change, but the correctness of the change is already obvious, and
> the readers would understand without being explained where the
> incorrectness we have to fix with this patch came from, I would think.
Future me would find that comment in the commit message very clarifying,
though: why was that code there? Ah, that's why.
Now I have to dig through the mailing list to find out.
Ciao,
Dscho
next prev parent reply other threads:[~2017-05-10 10:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-08 20:34 [PATCH v2] archive-tar: fix a sparse 'constant too large' warning Ramsay Jones
2017-05-09 10:24 ` Johannes Schindelin
2017-05-09 20:13 ` Ramsay Jones
2017-05-09 23:42 ` Junio C Hamano
2017-05-10 10:55 ` Johannes Schindelin [this message]
2017-05-09 23:36 ` Junio C Hamano
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=alpine.DEB.2.21.1.1705101254440.146734@virtualbox \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=ramsay@ramsayjones.plus.com \
/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).