From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH 0/2] getting rid of sha1_to_hex()
Date: Mon, 11 Nov 2019 23:53:38 +0000 [thread overview]
Message-ID: <20191111235338.GA9216@camp.crustytoothpaste.net> (raw)
In-Reply-To: <20191111092144.GA12607@sigill.intra.peff.net>
[-- Attachment #1: Type: text/plain, Size: 521 bytes --]
On 2019-11-11 at 09:21:44, Jeff King wrote:
> I actually worried that I might be stealing brian's thunder. But AFAICT
> this cleanup has been waiting for almost a year, so I figured it was
> fair game. :)
Oh, no, not at all. I'm delighted that it can go, and thanks for
sending the patches.
I think I had intended to remove it but hadn't because I was worried
about affecting topics in flight, and then promptly forgot about it.
--
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 868 bytes --]
prev parent reply other threads:[~2019-11-11 23:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 9:03 [PATCH 0/2] getting rid of sha1_to_hex() Jeff King
2019-11-11 9:04 ` [PATCH 1/2] hex: drop sha1_to_hex_r() Jeff King
2019-11-11 18:30 ` Johannes Schindelin
2019-11-11 9:04 ` [PATCH 2/2] hex: drop sha1_to_hex() Jeff King
2019-11-11 14:18 ` SZEDER Gábor
2019-11-11 14:29 ` Jeff King
2019-11-12 4:13 ` Junio C Hamano
2019-11-12 10:57 ` Jeff King
2019-11-12 11:44 ` SZEDER Gábor
2019-11-12 12:12 ` Jeff King
2019-11-12 11:49 ` Junio C Hamano
2019-11-12 12:15 ` Jeff King
2019-11-13 1:09 ` Junio C Hamano
2019-11-13 1:15 ` Jeff King
2019-11-11 9:09 ` [PATCH 0/2] getting rid of sha1_to_hex() Junio C Hamano
2019-11-11 9:21 ` Jeff King
2019-11-11 23:53 ` brian m. carlson [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191111235338.GA9216@camp.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.