Re: [PATCH v3 0/5] config-parse: create config parsing library
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Oct 27, 2023, 13:04 UTC
- Message-ID
- <xmqqjzr8p67g.fsf@gitster.g>
- In-Reply-To
- <ZTluW0Ha2W4NYaJd@google.com>
Josh Steadmon <steadmon@google.com> writes:
> Thanks everyone for the revived discussion here. I think I agree, this > series is not going in the right direction. Additionally, our internal > use case for this change has evaporated, so let's just drop the series. > We can pick it up again later if interest returns.
OK. Let's scrap it for now.
The "internal use case" behind a proposed feature changing so quickly is a bit worrying. What is good for this project should ideally be good for everybody, not only for satisfying a particular $CORP needs of the day. But I think the idea of giving enhanced visibility into stakeholder companies directions and priorities Emily (I think?) floated during the contributors' summit may help reduce such a risk, hopefully.
Thanks.