Note that there are some explanatory texts on larger screens.

plurals
  1. PODoes git log --branches work?
    primarykey
    data
    text
    <p>I can't seem to get <code>git log --branches</code> to correctly filter its output. It seems as if Git ignores it.</p> <p>For example, the head of <code>git log --graph --all --decorate</code>, prints:</p> <pre><code>* commit 3ae0d17538f787bdde68f37f6644ffe9652d8dc1 (HEAD, feature/branch-ignore) | Author: Chris Lewis &lt;chris@chris.to&gt; | Date: Mon Mar 14 17:39:56 2011 -0700 | | Ignore merge commits, as they're going to be duplicating events | * commit 770534e9d77acb03eaf842440c879aec1c5b5500 | Author: Chris Lewis &lt;chris@chris.to&gt; | Date: Tue Mar 8 14:39:40 2011 -0800 | | Removed another remote branch check | </code></pre> <p>Let's say I want to filter by <code>master</code>, which should mean these commits are ignored. The head of <code>git log --graph --all --decorate --branches=master</code>, is also:</p> <pre><code>* commit 3ae0d17538f787bdde68f37f6644ffe9652d8dc1 (HEAD, feature/branch-ignore) | Author: Chris Lewis &lt;chris@chris.to&gt; | Date: Mon Mar 14 17:39:56 2011 -0700 | | Ignore merge commits, as they're going to be duplicating events | * commit 770534e9d77acb03eaf842440c879aec1c5b5500 | Author: Chris Lewis &lt;chris@chris.to&gt; | Date: Tue Mar 8 14:39:40 2011 -0800 | | Removed another remote branch check | </code></pre> <p>Git doesn't seem to be filtering. It doesn't seem to make any difference whether <code>--branches</code> is passed with other arguments or not. My Git version is <code>git version 1.7.4.1</code>. Does anyone know how to use this command successfully?</p> <p>EDIT: All I want to be able to do is get the log of one branch or another, without having to do a checkout first.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

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