All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "René Scharfe" <l.s.r@web.de>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jul 2025, #02; Mon, 7)
Date: Wed, 09 Jul 2025 08:37:14 -0700	[thread overview]
Message-ID: <xmqqy0sxnzo5.fsf@gitster.g> (raw)
In-Reply-To: <861e6166-bda3-41c9-b259-2e46a77b6d84@web.de> ("René Scharfe"'s message of "Wed, 9 Jul 2025 11:25:55 +0200")

René Scharfe <l.s.r@web.de> writes:

> On 7/8/25 2:11 AM, Junio C Hamano wrote:
>> * rs/parse-options-precision (2025-06-29) 6 commits
>>  - parse-options: add precision handling for OPTION_COUNTUP
>>  - parse-options: add precision handling for OPTION_BITOP
>>  - parse-options: add precision handling for OPTION_NEGBIT
>>  - parse-options: add precision handling for OPTION_BIT
>>  - parse-options: add precision handling for OPTION_SET_INT
>>  - parse-options: add precision handling for PARSE_OPT_CMDMODE
>> 
>>  Define .precision to more canned parse-options type to avoid bugs
>>  coming from using a variable with a wrong type to capture the
>>  parsed values.
>> 
>>  Will merge to 'next'?
>>  source: <cf5cd57d-733f-4239-80f8-23bdc1523ab2@web.de>
> Will send v2 shortly.

Thanks for stopping me.


  reply	other threads:[~2025-07-09 15:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-08  0:11 What's cooking in git.git (Jul 2025, #02; Mon, 7) Junio C Hamano
2025-07-08  0:47 ` Ayush Chandekar
2025-07-09  9:25 ` René Scharfe
2025-07-09 15:37   ` Junio C Hamano [this message]
2025-07-09 10:41 ` Carlo Marcelo Arenas Belón
2025-07-09 14:15   ` Phillip Wood
2025-07-09 15:04   ` Johannes Sixt
2025-07-10  4:25     ` Carlo Marcelo Arenas Belón
2025-07-10  7:18       ` Johannes Sixt
2025-07-10 15:30         ` Junio C Hamano
2025-07-09 16:26   ` Junio C Hamano
2025-07-09 14:46 ` Taylor Blau
2025-07-10  0:01   ` Junio C Hamano
2025-07-10  1:05     ` Elijah Newren
2025-07-10  4:24       ` Junio C Hamano
2025-07-09 23:14 ` brian m. carlson
2025-07-10  4:24   ` Junio C Hamano

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=xmqqy0sxnzo5.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=l.s.r@web.de \
    /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.