From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] CoC: update to version 2.0 + local changes
Date: Wed, 13 Jan 2021 12:55:32 -0500 [thread overview]
Message-ID: <X/80FBlnrTlykI4B@coredump.intra.peff.net> (raw)
In-Reply-To: <xmqqr1mpxl4q.fsf@gitster.c.googlers.com>
On Wed, Jan 13, 2021 at 01:05:09AM -0800, Junio C Hamano wrote:
> > Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
> > Acked-by: Christian Couder <chriscool@tuxfamily.org>
> > Acked-by: Derrick Stolee <dstolee@microsoft.com>
> > Acked-by: Elijah Newren <newren@gmail.com>
> > Acked-by: Johannes Schindelin <johannes.schindelin@gmx.de>
> > Acked-by: Jonathan Nieder <jrnieder@gmail.com>
> > Acked-by: brian m. carlson <sandals@crustytoothpaste.net>
> > Signed-off-by: Junio C Hamano <gitster@pobox.com>
> > ---
>
> I guess I should lead by an example ;-) The above misses mine and
> Signed-off-by means a totally different thing [*1*] from Acked-by.
>
> Acked-by: Junio C Hamano <gitster@pobox.com>
I thought your "From" would be enough, but I see this re-wrapped version
if "From: Ævar" (so I guess my same argument applies for him ;) ).
Thanks for reposting this; I was trying hard not to look at my email
during the week of the original thread.
I agree with the sentiment expressed earlier that the "consequences" are
a little funny for us, since our decentralized infrastructure makes
things like banning a bit confusing. But that was already present to
some degree in the older version, and I do like the notion that we'd
stick to the original as closely as possible. So:
Acked-by: Jeff King <peff@peff.net>
-Peff
next prev parent reply other threads:[~2021-01-13 17:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-13 8:33 [PATCH] CoC: update to version 2.0 + local changes Junio C Hamano
2021-01-13 9:05 ` Junio C Hamano
2021-01-13 17:55 ` Jeff King [this message]
2021-01-13 15:25 ` Taylor Blau
2021-01-13 18:58 ` Jonathan Tan
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=X/80FBlnrTlykI4B@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).