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 (Oct 2023, #03; Fri, 6)
Date: Mon, 09 Oct 2023 09:35:07 -0700 [thread overview]
Message-ID: <xmqqcyxn3gas.fsf@gitster.g> (raw)
In-Reply-To: <4014e490-c6c1-453d-b0ed-645220e3e614@web.de> (=?utf-8?Q?=22R?= =?utf-8?Q?en=C3=A9?= Scharfe"'s message of "Sun, 8 Oct 2023 19:34:45 +0200")
René Scharfe <l.s.r@web.de> writes:
> Am 07.10.23 um 10:20 schrieb Junio C Hamano:
>> * rs/parse-options-value-int (2023-09-18) 2 commits
>> - parse-options: use and require int pointer for OPT_CMDMODE
>> - parse-options: add int value pointer to struct option
>> ...
> I don't mind removing this topic from seen for now; it's not ready, yet.
After seeing the discussion moved to giving a more type safe enum
support and then somehow convesation seemed to have petered out, I
was wondering if we figured out the problem space enough to see an
updated version with well defined scope and good problem
description. I do not mind keeping it on 'seen', especially if
these two early steps are not expected to change. It is not like
they are causing any maintenance burden.
Thanks.
next prev parent reply other threads:[~2023-10-09 16:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-07 8:20 What's cooking in git.git (Oct 2023, #03; Fri, 6) Junio C Hamano
2023-10-08 17:34 ` René Scharfe
2023-10-09 16:35 ` Junio C Hamano [this message]
2023-10-28 12:02 ` René Scharfe
2023-10-09 9:59 ` Phillip Wood
2023-10-09 16:16 ` Taylor Blau
2023-10-09 18:09 ` Junio C Hamano
2023-10-09 18:13 ` Taylor Blau
2023-10-09 21:07 ` Junio C Hamano
2023-10-10 20:36 ` Taylor Blau
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=xmqqcyxn3gas.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 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 NNTP newsgroup(s).