Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>To search for commit <em>content</em> (i.e., actual lines of source, as opposed to commit messages and the like), what you need to do is:</p> <pre><code>git grep &lt;regexp&gt; $(git rev-list --all) </code></pre> <p><strong>Updates</strong>: <code>git rev-list --all | xargs git grep expression</code> will work if you run into an "Argument list too long" error</p> <p>If you want to limit the search to some subtree (for instance "lib/util") you will need to pass that to the <code>rev-list</code> subcommand and <code>grep</code> as well:</p> <pre><code>git grep &lt;regexp&gt; $(git rev-list --all -- lib/util) -- lib/util </code></pre> <p>This will grep through all your commit text for regexp.</p> <p>The reason for passing the path in both commands is because <code>rev-list</code> will return the revisions list where all the changes to <code>lib/util</code> happened, but also you need to pass to <code>grep</code> so that it will only search on <code>lib/util</code>.</p> <p>Just imagine the following scenario: <code>grep</code> might find the same <code>&lt;regexp&gt;</code> on other files which are contained in the same revision returned by <code>rev-list</code> (even if there was no change to that file on that revision).</p> <p>Here are some other useful ways of searching your source:</p> <p>Search working tree for text matching regular expression regexp:</p> <pre><code>git grep &lt;regexp&gt; </code></pre> <p>Search working tree for lines of text matching regular expression regexp1 or regexp2:</p> <pre><code>git grep -e &lt;regexp1&gt; [--or] -e &lt;regexp2&gt; </code></pre> <p>Search working tree for lines of text matching regular expression regexp1 and regexp2, reporting file paths only:</p> <pre><code>git grep -e &lt;regexp1&gt; --and -e &lt;regexp2&gt; </code></pre> <p>Search working tree for files that have lines of text matching regular expression regexp1 and lines of text matching regular expression regexp2:</p> <pre><code>git grep -l --all-match -e &lt;regexp1&gt; -e &lt;regexp2&gt; </code></pre> <p>Search working tree for changed lines of text matching pattern:</p> <pre><code>git diff --unified=0 | grep &lt;pattern&gt; </code></pre> <p>Search all revisions for text matching regular expression regexp:</p> <pre><code>git grep &lt;regexp&gt; $(git rev-list --all) </code></pre> <p>Search all revisions between rev1 and rev2 for text matching regular expression regexp:</p> <pre><code>git grep &lt;regexp&gt; $(git rev-list &lt;rev1&gt;..&lt;rev2&gt;) </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POHow to grep (search) committed code in the git history?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USIulian Onofrei
    1. USJeet
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow to grep (search) committed code in the git history?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COThanks, works great! It's sad though that "$(git rev-list --all)" is needed and no convenient switch to specify searching in the whole history of a branch.
      singulars
      1. PO
      1. USOrtwin Gentz
    2. COExcellent. +1. The GitBook add some details (http://book.git-scm.com/4_finding_with_git_grep.html), and Junio C Hamano illustrates some of your points: http://gitster.livejournal.com/27674.html
      singulars
      1. PO
      1. USVonC
    3. COUnfortunately, I cannot get this going with msysgit-1.7.4. It tells me `sh.exe": /bin/git: Bad file number`. VonC's answer also works with msysgit.
      singulars
      1. PO
      1. USeckes
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload