Skip to content

Commit 12310ed

Browse files
committed
A little section on git log
1 parent 46cd62a commit 12310ed

File tree

1 file changed

+18
-2
lines changed

1 file changed

+18
-2
lines changed

index.html

Lines changed: 18 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -140,9 +140,25 @@ <h2>tagging</h2>
140140
<p>
141141
it's recommended to create tags for software releases. this is a known concept, which also exists in SVN. You can create a new tag named <i>1.0.0</i> by executing<br />
142142
<code>git tag 1.0.0 1b2e1d63ff</code><br />
143-
the <i>1b2e1d63ff</i> stands for the first 10 characters of the commit id you want to reference with your tag. You can get the commit id with <br />
143+
the <i>1b2e1d63ff</i> stands for the first 10 characters of the commit id you want to reference with your tag. You can get the commit id by looking at the... <br />
144+
</p>
145+
</div>
146+
<a name="log"></a>
147+
<div class="scrollblock block-log">
148+
<h2>log</h2>
149+
<p>
150+
in its simplest form, you can study repository history using..
144151
<code>git log</code><br />
145-
you can also use fewer characters of the commit id, it just has to be unique.
152+
You can add a lot of parameters to make the log look like what you want. To see only the commits of a certain author:<br />
153+
<code>git log --author=bob</code><br />
154+
To see a very compressed log where each commit is one line:<br />
155+
<code>git log --pretty=oneline</code><br />
156+
Or mabe you want to see an ASCII art tree of all the branches, decorated with the names of tags and branches: <br />
157+
<code>git log --graph --oneline --decorate --all</code><br />
158+
See only which files have changed: <br />
159+
<code>git log --name-status</code><br />
160+
These are just a few of the possible parameters you can use. For more, see
161+
<code>git log --help</code><br />
146162
</p>
147163
</div>
148164
<a name="checkout-replace"></a>

0 commit comments

Comments
 (0)