Re: [PATCHv2] gitweb: Better regexp for SHA-1 committag match
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Feb 7, 2009, 08:48 UTC
- Message-ID
- <7v7i42y6ms.fsf@gitster.siamese.dyndns.org>
- In-Reply-To
- <200902070934.50555.jnareb@gmail.com>
Jakub Narebski <jnareb@gmail.com> writes:
Show 7 quoted lines
> It would unfortunately falsely match... but we cannot eliminate this > case (well, at least not checking if hexnumber is followed by dot), > because of totally legitimate > > ... at commit 8457bb9e. > > So even with that we would have still false matches...
Yeah, so what's the value in v2 over v1? It is still wrong but it is less wrong than it used to be? I think the word-boundary one made a good sense. I do not see the @lookahead adding much value at all.