All of lore.kernel.org
 help / color / mirror / Atom feed
From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC PATCH 1/6] hex: add functionality for lowercase-only hex
Date: Tue, 25 Aug 2026 21:44:11 +0000	[thread overview]
Message-ID: <ao4MqtDxZJaMEBBI@fruit.crustytoothpaste.net> (raw)
In-Reply-To: <xmqq5x0yp5ts.fsf@gitster.g>

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

On 2026-08-25 at 15:39:43, Junio C Hamano wrote:
> "brian m. carlson" <sandals@crustytoothpaste.net> writes:
> 
> > We currently allow both upper and lower case for all hex values in Git.
> > However, in a future commit, we'll want to change that to allow only
> > lowercase values in some cases.  To prepare for that case, provide a
> > table to convert hex values using lowercase only and an enum to let us
> > choose which we want, wiring it up to the hexval function.
> >
> > For now, keep things completely the same by specifying only the
> > variant that accepts both lowercase and uppercase to avoid changing
> > behavior.
> >
> > Signed-off-by: brian m. carlson <sandals@crustytoothpaste.net>
> > ---
> >  color.c    |  2 +-
> >  hex-ll.c   | 37 ++++++++++++++++++++++++++++++++++++-
> >  hex-ll.h   | 14 ++++++++++----
> >  pkt-line.c |  8 ++++----
> >  4 files changed, 51 insertions(+), 10 deletions(-)
> 
> 
> Now this is an embarrassingly late review.  I hope this is not a
> sign that nobody is paying attention on the list these days X-<.
> 
> > +const signed char hexval_lc_table[256] = {
> > +	 -1, -1, -1, -1, -1, -1, -1, -1,		/* 00-07 */
> > +	 -1, -1, -1, -1, -1, -1, -1, -1,		/* 08-0f */
> > +	 -1, -1, -1, -1, -1, -1, -1, -1,		/* 10-17 */
> > +	 -1, -1, -1, -1, -1, -1, -1, -1,		/* 18-1f */
> > +	 -1, -1, -1, -1, -1, -1, -1, -1,		/* 20-27 */
> > +	 -1, -1, -1, -1, -1, -1, -1, -1,		/* 28-2f */
> > +	  0,  1,  2,  3,  4,  5,  6,  7,		/* 30-37 */
> > +	  8,  9, -1, -1, -1, -1, -1, -1,		/* 38-3f */
> > +	 -1, -1, -1, -1, -1, -1, -1, -1,		/* 40-47 */
> > +	 -1, -1, -1, -1, -1, -1, -1, -1,		/* 48-4f */
> > +	 -1, -1, -1, -1, -1, -1, -1, -1,		/* 50-57 */
> > +	 -1, -1, -1, -1, -1, -1, -1, -1,		/* 58-5f */
> > +	 -1, 10, 11, 12, 13, 14, 15, -1,		/* 60-67 */
> > +	 -1, -1, -1, -1, -1, -1, -1, -1,		/* 68-67 */
> 
> That's 68-6f if I am not mistaken ;-).

So it is.  Will fix in v2.

I think I accidentally included the uppercase but not lowercase variants
when creating the original array and then copied and pasted the line,
but messed up the comment.
-- 
brian m. carlson (they/them)
Toronto, Ontario, CA

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

  reply	other threads:[~2026-08-25 21:44 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-29 23:32 [RFC PATCH 0/6] Git 3.0: restrict hex object IDs to lowercase only brian m. carlson
2026-07-29 23:32 ` [RFC PATCH 1/6] hex: add functionality for lowercase-only hex brian m. carlson
2026-07-31  7:38   ` Junio C Hamano
2026-08-25 15:39   ` Junio C Hamano
2026-08-25 21:44     ` brian m. carlson [this message]
2026-07-29 23:32 ` [RFC PATCH 2/6] hex: allow specifying hex type with hex2chr brian m. carlson
2026-07-29 23:32 ` [RFC PATCH 3/6] hex: make hex_to_bytes accept kind of hex to use brian m. carlson
2026-07-31  7:38   ` Junio C Hamano
2026-08-01 14:35     ` Jeff King
2026-07-29 23:32 ` [RFC PATCH 4/6] hex: label usages of hex parsing for object IDs brian m. carlson
2026-07-31  3:24   ` Junio C Hamano
2026-08-25 16:11   ` Junio C Hamano
2026-07-29 23:32 ` [RFC PATCH 5/6] object-name: use hexval brian m. carlson
2026-08-25 16:19   ` Junio C Hamano
2026-08-25 19:44   ` Elijah Newren
2026-08-25 21:41     ` brian m. carlson
2026-07-29 23:32 ` [RFC PATCH 6/6] hex: allow only lowercase object IDs in breaking changes mode brian m. carlson
2026-07-31  7:48   ` Junio C Hamano
2026-07-31 12:33     ` Junio C Hamano
2026-08-02 22:09     ` brian m. carlson
2026-08-04 19:32       ` Junio C Hamano
2026-08-04 21:46         ` brian m. carlson
2026-08-05  3:09       ` Michael Montalbo
2026-08-25  9:04   ` Phillip Wood
2026-08-25 21:36     ` brian m. carlson
2026-08-25 16:36   ` Junio C Hamano
2026-08-25 19:44   ` Elijah Newren
2026-07-30  8:21 ` [RFC PATCH 0/6] Git 3.0: restrict hex object IDs to lowercase only Junio C Hamano
2026-07-30 21:18   ` brian m. carlson
2026-08-01 14:45     ` Jeff King
2026-08-01 18:22       ` Junio C Hamano
2026-08-02 21:55       ` brian m. carlson

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=ao4MqtDxZJaMEBBI@fruit.crustytoothpaste.net \
    --to=sandals@crustytoothpaste.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.
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.