From: Junio C Hamano <gitster@pobox.com>
To: mwnx <mwnx@gmx.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] pretty: fix buffer over-read with %> and %<
Date: Tue, 28 Nov 2017 11:10:20 +0900 [thread overview]
Message-ID: <xmqqtvxf886r.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20171127232927.x5iamt5rlxrafkhe@debian> (mwnx@gmx.com's message of "Tue, 28 Nov 2017 00:29:27 +0100")
mwnx <mwnx@gmx.com> writes:
> On Mon, Nov 27, 2017 at 10:46:23AM +0900, Junio C Hamano wrote:
>> By the way, Documentation/SubmittingPatches has this in "(5) Certify
>> your work" section:
>>
>> Also notice that a real name is used in the Signed-off-by: line. Please
>> don't hide your real name.
>
> (especially since I'm not quite sure what the rationale behind it
> is).
As DCO is something we'd need to present to the court when the next
SCO comes after us, we'd prefer to see that we can refer to, and
contact if necessary, a real person when we need to say "this is not
a stolen code, here is the person who presented it to us and we'll
let him or her explain".
> What are your thoughts on this issue?
Not limited to this, but our stance for things are that previous
mistakes do not justify repeating and spreading the same.
next prev parent reply other threads:[~2017-11-28 2:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-26 2:52 [PATCH] pretty: fix buffer over-read with %> and %< mwnx
2017-11-27 1:46 ` Junio C Hamano
2017-11-27 23:29 ` mwnx
2017-11-28 2:10 ` Junio C Hamano [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-11-29 0:32 mwnx
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqtvxf886r.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=mwnx@gmx.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).