| 4 |
<head> |
<head> |
| 5 |
<title>ViewVC Help: Query The Commit Database</title> |
<title>ViewVC Help: Query The Commit Database</title> |
| 6 |
<link rel="stylesheet" href="help.css" type="text/css" /> |
<link rel="stylesheet" href="help.css" type="text/css" /> |
| 7 |
|
<link rel="shortcut icon" href="images/favicon.ico" type="image/x-icon" /> |
| 8 |
|
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" /> |
| 9 |
</head> |
</head> |
| 10 |
<body> |
<body> |
| 11 |
<table> |
<div><a href="http://viewvc.org/index.html"><img src="images/viewvc-logo.png" alt="ViewVC logotype" /></a></div> |
| 12 |
<col class="menu" /> |
<table> |
| 13 |
<col /> |
<col class="menu" /> |
| 14 |
<tr> |
<col /> |
| 15 |
<td><a href=".."><img |
<tr><td> |
| 16 |
src="images/logo.png" alt="ViewVC logotype" /></a> |
<h3>Help:</h3> |
| 17 |
</td> |
<a href="help_rootview.html">General</a><br /> |
| 18 |
<td><h1>ViewVC Help: Query The Commit Database</h1></td> |
<a href="help_dirview.html">Directory View</a><br /> |
| 19 |
</tr> |
<a href="help_log.html">Log View</a><br /> |
| 20 |
<tr><td> |
<strong>Query Database</strong> |
| 21 |
<h3>Other Help:</h3> |
</td><td> |
| 22 |
<a href="help_rootview.html">General</a><br /> |
|
| 23 |
<a href="help_dirview.html">Directory View</a><br /> |
<h1>ViewVC Help: Query The Commit Database</h1> |
| 24 |
<a href="help_log.html">Classic Log View</a><br /> |
|
| 25 |
<a href="help_logtable.html">Alternative Log View</a><br /> |
<p> |
| 26 |
<strong>Query Database</strong> |
Select your parameters for querying the CVS commit database in the |
| 27 |
|
form at the top of the page. You |
| 28 |
<h3>Internet</h3> |
can search for multiple matches by typing a comma-seperated list |
| 29 |
<a href="http://viewvc.org/index.html">Home</a><br /> |
into the text fields. Regular expressions, and wildcards are also |
| 30 |
<a href="http://viewvc.org/upgrading.html">Upgrading</a><br /> |
supported. Blank text input fields are treated as wildcards. |
| 31 |
<a href="http://viewvc.org/contributing.html">Contributing</a><br /> |
</p> |
| 32 |
<a href="http://viewvc.org/license-1.html">License</a><br /> |
<p> |
| 33 |
</td><td colspan="2"> |
Any of the text entry fields can take a comma-seperated list of |
| 34 |
|
search arguments. For example, to search for all commits from |
| 35 |
<p> |
authors <em>jpaint</em> and <em>gstein</em>, just type: <code>jpaint, |
| 36 |
Select your parameters for querying the CVS commit database in the |
gstein</code> in the <em>Author</em> input box. If you are searching |
| 37 |
form at the top of the page. You |
for items containing spaces or quotes, you will need to quote your |
| 38 |
can search for multiple matches by typing a comma-seperated list |
request. For example, the same search above with quotes is: |
| 39 |
into the text fields. Regular expressions, and wildcards are also |
<code>"jpaint", "gstein"</code>. |
| 40 |
supported. Blank text input fields are treated as wildcards. |
</p> |
| 41 |
</p> |
<p> |
| 42 |
<p> |
Wildcard and regular expression searches are entered in a similar |
| 43 |
Any of the text entry fields can take a comma-seperated list of |
way to the quoted requests. You must quote any wildcard or |
| 44 |
search arguments. For example, to search for all commits from |
regular expression request, and a command character preceeds the |
| 45 |
authors <em>jpaint</em> and <em>gstein</em>, just type: <code>jpaint, |
first quote. The command character <code>l</code>(lowercase L) is for wildcard |
| 46 |
gstein</code> in the <em>Author</em> input box. If you are searching |
searches, and the wildcard character is a percent (<code>%</code>). The |
| 47 |
for items containing spaces or quotes, you will need to quote your |
command character for regular expressions is <code>r</code>, and is |
| 48 |
request. For example, the same search above with quotes is: |
passed directly to MySQL, so you'll need to refer to the MySQL |
| 49 |
<code>"jpaint", "gstein"</code>. |
manual for the exact regex syntax. It is very similar to Perl. A |
| 50 |
</p> |
wildard search for all files with a <em>.py</em> extention is: |
| 51 |
<p> |
<code>l"%.py"</code> in the <em>File</em> input box. The same search done |
| 52 |
Wildcard and regular expression searches are entered in a similar |
with a regular expression is: <code>r".*\.py"</code>. |
| 53 |
way to the quoted requests. You must quote any wildcard or |
</p> |
| 54 |
regular expression request, and a command character preceeds the |
<p> |
| 55 |
first quote. The command character <code>l</code>(lowercase L) is for wildcard |
All search types can be mixed, as long as they are seperated by |
| 56 |
searches, and the wildcard character is a percent (<code>%</code>). The |
commas. |
| 57 |
command character for regular expressions is <code>r</code>, and is |
</p> |
| 58 |
passed directly to MySQL, so you'll need to refer to the MySQL |
</td></tr></table> |
| 59 |
manual for the exact regex syntax. It is very similar to Perl. A |
<hr /> |
| 60 |
wildard search for all files with a <em>.py</em> extention is: |
<address><a href="mailto:users@viewvc.tigris.org">ViewVC Users Mailinglist</a></address> |
| 61 |
<code>l"%.py"</code> in the <em>File</em> input box. The same search done |
</body> |
| 62 |
with a regular expression is: <code>r".*\.py"</code>. |
</html> |
|
</p> |
|
|
<p> |
|
|
All search types can be mixed, as long as they are seperated by |
|
|
commas. |
|
|
</p> |
|
|
</td></tr></table> |
|
|
</body></html> |
|
Parent Directory
| 
Revision Log
| 
Patch