All of lore.kernel.org
 help / color / mirror / Atom feed
From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
	"Miriam R." <mirucam@gmail.com>
Subject: Re: [PATCH] run-command: avoid undefined behavior in exists_in_PATH
Date: Wed, 8 Jan 2020 02:47:32 +0000	[thread overview]
Message-ID: <20200108024732.GL6570@camp.crustytoothpaste.net> (raw)
In-Reply-To: <20200107110145.GA1073219@coredump.intra.peff.net>

[-- Attachment #1: Type: text/plain, Size: 638 bytes --]

On 2020-01-07 at 11:01:45, Jeff King wrote:
> > Noticed-by: Miriam R. <mirucam@gmail.com>
> > Signed-off-by: brian m. carlson <sandals@crustytoothpaste.net>
> 
> 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.
-- 
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 868 bytes --]

  parent reply	other threads:[~2020-01-08  2:47 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 [this message]
2020-01-08  9:15     ` Miriam R.
2020-01-08 10:28       ` Christian Couder

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=20200108024732.GL6570@camp.crustytoothpaste.net \
    --to=sandals@crustytoothpaste.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=mirucam@gmail.com \
    --cc=peff@peff.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.