From: Taylor Blau <firstname.lastname@example.org> To: Junio C Hamano <email@example.com> Cc: firstname.lastname@example.org, Johannes Schindelin <Johannes.Schindelin@gmx.de> Subject: Re: Raise your hand to Ack jk/code-of-conduct if your Ack fell thru cracks Date: Tue, 8 Oct 2019 17:22:46 -0700 [thread overview] Message-ID: <20191009002246.GA25840@syl.local> (raw) In-Reply-To: <email@example.com> On Wed, Oct 09, 2019 at 09:14:59AM +0900, Junio C Hamano wrote: > Johannes Schindelin <Johannes.Schindelin@gmx.de> writes: > > > In other words, the commit message can be augmented by this: > > > > Acked-by: Johannes Schindelin <firstname.lastname@example.org> > > Acked-by: Derrick Stolee <email@example.com> > > Acked-by: Garima Singh <firstname.lastname@example.org> > > Acked-by: Jonathan Tan <email@example.com> > > Acked-by: Thomas Gummerer <firstname.lastname@example.org> > > Acked-by: brian m. carlson <email@example.com> > > Acked-by: Elijah Newren <firstname.lastname@example.org> > > > > Junio, would you mind picking it up, please? > > I trust you enough that I won't go back to the cited messages to > double check that these acks are real, but I'd still wait for a few > days for people who expressed their Acks but your scan missed, or > those who wanted to give their Acks but forgot to do so, to raise > their hands on this thread. I'd be quite pleased to join those above with my strongest: Acked-by: Taylor Blau <email@example.com> I admit to waiting a couple of days before responding to that originally linked thread, and that by the time I got around to readying a reply, everything that I wanted to say in favor of a CoC was already well put by others. So, I don't think that I have anything more to add than to say that I think it's great, that we should have it, and that I most certainly approve of the direction of that patch. Thanks, Taylor
next prev parent reply other threads:[~2019-10-09 0:22 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-10-07 3:38 What's cooking in git.git (Oct 2019, #02; Mon, 7) Junio C Hamano 2019-10-08 19:36 ` jk/code-of-conduct, was " Johannes Schindelin 2019-10-09 0:14 ` Raise your hand to Ack jk/code-of-conduct if your Ack fell thru cracks Junio C Hamano 2019-10-09 0:22 ` Taylor Blau [this message] 2019-10-09 1:41 ` Emily Shaffer 2019-10-09 8:07 ` Johannes Schindelin 2019-10-09 1:48 ` Jonathan Nieder 2019-10-09 10:36 ` Christian Couder 2019-10-09 15:13 ` Phillip Wood 2019-10-09 18:29 ` Elijah Newren 2019-10-09 19:37 ` Junio C Hamano 2019-10-09 19:52 ` William Baker 2019-10-09 20:50 ` CB Bailey 2019-10-10 0:18 ` Eric Wong 2019-10-11 5:58 ` Jeff King 2019-10-17 13:56 ` Philip Oakley 2019-10-11 4:39 ` Junio C Hamano 2019-10-11 6:01 ` Jeff King 2019-10-09 1:39 ` jk/code-of-conduct, was Re: What's cooking in git.git (Oct 2019, #02; Mon, 7) SZEDER Gábor
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=20191009002246.GA25840@syl.local \ --firstname.lastname@example.org \ --cc=Johannes.Schindelin@gmx.de \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Raise your hand to Ack jk/code-of-conduct if your Ack fell thru cracks' \ /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
Code repositories for project(s) associated with this 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).