| Issue 2925: | Searching for comments does not work | |
| 1 person starred this issue and may be notified of changes. | Back to list |
************************************************************ ***** NOTE: THIS BUG TRACKER IS FOR GERRIT CODE REVIEW ***** ***** DO NOT SUBMIT BUGS FOR CHROME, ANDROID, INTERNAL ***** ***** ISSUES WITH YOUR COMPANY'S GERRIT SETUP, ETC. ***** ***** THOSE ISSUE BELONG IN DIFFERENT ISSUE TRACKERS! ***** ************************************************************ Affected Version: 2.8.6.1, gerrit.libreoffice.org What steps will reproduce the problem? 1.1 in the search field enter "comment:dupes" and hit "Search": 1.2 it comes up with a long list of hits, among them <https://gerrit.libreoffice.org/#/c/10978/>; click on that, click on "Expand All", search for "dupes" on that web page gives no hit 2.1 in the search field enter "__GNUC__" and hit "Search": 2.2 it comes up with an empty list of hits, even though <https://gerrit.libreoffice.org/#/c/9407/1> contains that string in the third comment in the history
Sep 23, 2014
#1
dborowitz@google.com
Sep 23, 2014
Ugh, hit save too soon. Can you reproduce (1) with some other words?
Sep 23, 2014
re (1): no, "comment:bottom" also brings up a long list including seemingly non-hits like <https://gerrit.libreoffice.org/#/c/11596/> (though that one e.g. mentions "button"---I wonder if this is due to a too fuzzy search engine?) re (2): (just to clarify, I meant "comment:__GNUC__" there, not just "__GNUC__", which would result in an error page)
Sep 24, 2014
"(2) is related to issue 2822 , but it sounds like you want the opposite behavior?": but "__GNUC__" appears as a single word surrounded by spaces in <https://gerrit.libreoffice.org/#/c/9407/1> (though as part of an "inline" comment, maybe that's what makes a difference?), and my understanding of issue 2822 is that it relates to sub-word matches? |
|
| ► Sign in to add a comment |