Re: [PATCH v2] grep: avoid setting UTF mode when dangerous with PCRE

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [PATCH v2] grep: avoid setting UTF mode when dangerous with PCRE
From: Carlo Arenas <carenas@xxxxxxxxx>
Date: Thu, 18 Nov 2021 02:15:49 -0800
Cc: git@xxxxxxxxxxxxxxx, avarab@xxxxxxxxx, someguy@xxxxxxxxxxxxxxxxxxx, René Scharfe <l.s.r@xxxxxx>, Andreas Schwab <schwab@xxxxxxxxxxxxxx>
In-reply-to: <xmqqpmqxyla3.fsf@gitster.g>
References: <20211116110035.22140-1-carenas@gmail.com> <20211117102329.95456-1-carenas@gmail.com> <xmqqpmqxyla3.fsf@gitster.g>

On Wed, Nov 17, 2021 at 11:29 PM Junio C Hamano <gitster@xxxxxxxxx> wrote:
>
> So, is this the final verrsion everybody is happy with, instead of
> just reverting the whole "paint hits in log --grep" topic, or did I
> miss more discussion in the original thread?

This will likely need at least some ACKs.

Apologies for the noise.

Carlo

Follow-Ups:
- Re: [PATCH v2] grep: avoid setting UTF mode when dangerous with PCRE
  - From: Hamza Mahfooz

References:
- [PATCH] grep: avoid setting UTF mode when not needed
  - From: Carlo Marcelo Arenas Belón
- [PATCH v2] grep: avoid setting UTF mode when dangerous with PCRE
  - From: Carlo Marcelo Arenas Belón
- Re: [PATCH v2] grep: avoid setting UTF mode when dangerous with PCRE
  - From: Junio C Hamano

Prev by Date: Re: [PATCH 1/2] grep/pcre2: limit the instances in which UTF mode is enabled
Next by Date: [PATCH v2] fetch-pack: parameterize message containing 'ready' keyword
Previous by thread: Re: [PATCH v2] grep: avoid setting UTF mode when dangerous with PCRE
Next by thread: Re: [PATCH v2] grep: avoid setting UTF mode when dangerous with PCRE
Index(es):
- Date
- Thread

[Index of Archives] [Linux Kernel Development] [Gcc Help] [IETF Annouce] [DCCP] [Netdev] [Networking] [Security] [V4L] [Bugtraq] [Yosemite] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Linux SCSI] [Fedora Users]