From: Christian Couder <christian.couder@gmail.com>
To: "Miriam R." <mirucam@gmail.com>
Cc: "brian m. carlson" <sandals@crustytoothpaste.net>,
Jeff King <peff@peff.net>, git <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] run-command: avoid undefined behavior in exists_in_PATH
Date: Wed, 8 Jan 2020 11:28:51 +0100 [thread overview]
Message-ID: <CAP8UFD246PpsysJd8s37g+BjSu4NNerW_ozEMtkP9iGCmUbupQ@mail.gmail.com> (raw)
In-Reply-To: <CAN7CjDCv2uYNaHEtQv6Zco33-Cba1Fn2by87NU_3vwytZHy_WA@mail.gmail.com>
On Wed, Jan 8, 2020 at 10:16 AM Miriam R. <mirucam@gmail.com> wrote:
>
> El mié., 8 ene. 2020 a las 3:47, brian m. carlson
> (<sandals@crustytoothpaste.net>) escribió:
> > > I think Miriam actually posted the same patch in her initial email:
> > >
> > > https://lore.kernel.org/git/CAN7CjDDBA0ZoCG9aaQf5rg3gxqny=EjR6v6jE1mnxvUJQSF_0Q@mail.gmail.com/
> > >
> > > I don't know how we want to handle authorship.
> >
> > I don't feel strongly about holding authorship; I'm happy to have her
> > name on it instead of mine since she did propose a solution. I just
> > care that we fix it.
> my mentor (Christian Couder <chriscool@tuxfamily.org>) was who
> detected the problem and sent me the solution, I only asked the
> community. I think his name should be in the patch instead of mine.
I am ok with not having my name anywhere and leaving the patch as is.
prev parent reply other threads:[~2020-01-08 10:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 1:36 [PATCH] run-command: avoid undefined behavior in exists_in_PATH brian m. carlson
2020-01-07 2:04 ` Jonathan Nieder
2020-01-07 2:16 ` brian m. carlson
2020-01-07 3:40 ` Bryan Turner
2020-01-07 3:41 ` Bryan Turner
2020-01-07 11:08 ` Jeff King
2020-01-07 11:01 ` Jeff King
2020-01-07 16:58 ` Junio C Hamano
2020-01-08 2:47 ` brian m. carlson
2020-01-08 9:15 ` Miriam R.
2020-01-08 10:28 ` Christian Couder [this message]
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=CAP8UFD246PpsysJd8s37g+BjSu4NNerW_ozEMtkP9iGCmUbupQ@mail.gmail.com \
--to=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mirucam@gmail.com \
--cc=peff@peff.net \
--cc=sandals@crustytoothpaste.net \
/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).