about summary refs log tree commit homepage
path: root/contrib
diff options
context:
space:
mode:
authorEric Wong <e@80x24.org>2019-10-31 03:12:20 +0000
committerEric Wong <e@80x24.org>2019-10-31 03:12:38 +0000
commit3f4a8611c37294a1938ae5ac644c24290d1d14ae (patch)
tree29cfdbf0d116b0506a6b513f52cfc9a270b2fde6 /contrib
parente5cc97f6a2ff53f072a5d692e56d0918b33c5081 (diff)
downloadpublic-inbox-3f4a8611c37294a1938ae5ac644c24290d1d14ae.tar.gz
When solving for blob 81c1164ae5 in https://public-inbox.org/git/,
at least two messages get indexed with the dfpost result for
that blob (after fixing MsgIter to decode all text/* parts):

1. https://public-inbox.org/git/b9fb52b8-8168-6bf0-9a72-1e6c44a281a5@oracle.com/
2. https://public-inbox.org/git/56664222-6c29-09dc-ef78-7b380b113c4a@oracle.com/

However, only the first message contains a usable patch.  So
we must adjust SolverGit to account for multiple messages
hitting the same "dfpost:" search result and attempt
"git apply" on all results, not just the first.

In the future, changes to SearchIdx.pm may rid us of invalid
search results and speed up performance (at the expense of
developer/indexing time); but we need to account for old search
indices, first.
Diffstat (limited to 'contrib')
0 files changed, 0 insertions, 0 deletions