Commit | Line | Data |
2646511e |
1 | <p><strong>Pattern</strong> is by default a normal string that is matched precisely (but without |
2 | regard to case, except in the case of pickaxe). However, when you check the <em>re</em> checkbox, |
3 | the pattern entered is recognized as the POSIX extended |
4 | <a href="http://en.wikipedia.org/wiki/Regular_expression">regular expression</a> (also case |
5 | insensitive).</p> |
6 | <dl> |
7 | <dt><b>commit</b></dt> |
8 | <dd>The commit messages and authorship information will be scanned for the given pattern.</dd> |
9 | |
10 | <dt><b>grep</b></dt> |
11 | <dd>All files in the currently selected tree (HEAD unless you are explicitly browsing |
12 | a different one) are searched for the given pattern. On large trees, this search can take |
13 | a while and put some strain on the server, so please use it with some consideration. Note that |
14 | due to git-grep peculiarity, currently if regexp mode is turned off, the matches are |
15 | case-sensitive.</dd> |
16 | <dt><b>author</b></dt> |
17 | <dd>Name and e-mail of the change author and date of birth of the patch will be scanned for the given pattern.</dd> |
18 | <dt><b>committer</b></dt> |
19 | <dd>Name and e-mail of the committer and date of commit will be scanned for the given pattern.</dd> |
20 | <dt><b>pickaxe</b></dt> |
21 | <dd>All commits that caused the string to appear or disappear from any file (changes that |
22 | added, removed or "modified" the string) will be listed. This search can take a while and |
23 | takes a lot of strain on the server, so please use it wisely. Note that since you may be |
24 | interested even in changes just changing the case as well, this search is case sensitive.</dd> |
25 | </dl> |
26 | |