Re: [PATCH 3/3] gitweb: Link to "git describe"'d commits in log messages
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Sep 21, 2016, 18:01 UTC
- Message-ID
- <xmqqy42l874n.fsf@gitster.mtv.corp.google.com>
- In-Reply-To
- <ba9d9c82-4b5e-4d62-95f1-a1c56cfc70af@gmail.com>
Jakub Narębski <jnareb@gmail.com> writes:
Show 6 quoted lines
>> When I saw 2/3 I wondered about one thing and 3/3 shares the same, >> which is that we only use regex match and do not validate for a >> false match. Would it be too expensive... > > It's a matter of balance between false positives (and unresolving > links) and performance...
Yes, and that is why I asked a simple yes-or-no question. Would it be too expensive? Your answer seems to be yes.
Have we measured? Is that really a bottleneck? Would it help to update parse_commits to call a new command "gitweb--helper" that produces the result of what git_print_log would have done to its $log argument, for example?