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