Re: [PATCH] setup: warn about un-enabled extensions
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Jul 15, 2020, 19:16 UTC
- Message-ID
- <nycvar.QRO.7.76.6.2007152115021.52@tvgsbejvaqbjf.bet>
- In-Reply-To
- <3544e544-0ed5-c2d7-ff25-ad6d9349905e@gmail.com>
Hi,
On Wed, 15 Jul 2020, Derrick Stolee wrote:
Show 33 quoted lines
> On 7/15/2020 2:09 PM, Junio C Hamano wrote:
> > Derrick Stolee <stolee@gmail.com> writes:
> >
> >> Your previous diff had this comment, which I thought to be
> >> helpful:
> >>
> >> + /*
> >> + * Extensions are added by more "} else if (...) {"
> >> + * lines here, but do NOT mark them as allowed in v0
> >> + * by copy-pasting without thinking.
> >> + */
> >
> > Yeah, but it felt somewhat strange to have it at the end of one
> > entry, like this:
> >
> > + unallowed_in_v0 = 0;
> > } else if (!strcmp(ext, "worktreeconfig")) {
> > data->worktree_config = git_config_bool(var, value);
> > + unallowed_in_v0 = 0;
> > + /*
> > + * Extensions are added by more "} else if (...) {"
> > + * lines here, but do NOT mark them as allowed in v0
> > + * by copy-pasting without thinking.
> > + */
> > + } else {
> > string_list_append(&data->unknown_extensions, ext);
> >
> >
> > In any case, I updated the comment in front of the if/else if/
> > cascade to essentially say the same thing, and with test updates
> > this time.
>
> Thanks. I applied and tested this version. LGTM!Sorry for being slow at the party; I'd much rather deal with Git issues than with the paperwork I am fighting with.
Thank you for working on this, I am pretty happy with the state you whipped it into, but take that with a grain of salt, as my brain is moosh.
Ciao, Dscho