]> git.ipfire.org Git - thirdparty/git.git/blob - Documentation/git-log.txt
Documentation: rename gitlink macro to linkgit
[thirdparty/git.git] / Documentation / git-log.txt
1 git-log(1)
2 ==========
3
4 NAME
5 ----
6 git-log - Show commit logs
7
8
9 SYNOPSIS
10 --------
11 'git-log' <option>...
12
13 DESCRIPTION
14 -----------
15 Shows the commit logs.
16
17 The command takes options applicable to the linkgit:git-rev-list[1]
18 command to control what is shown and how, and options applicable to
19 the linkgit:git-diff-tree[1] commands to control how the changes
20 each commit introduces are shown.
21
22 This manual page describes only the most frequently used options.
23
24
25 OPTIONS
26 -------
27
28 include::pretty-options.txt[]
29
30 :git-log: 1
31 include::diff-options.txt[]
32
33 -<n>::
34 Limits the number of commits to show.
35
36 <since>..<until>::
37 Show only commits between the named two commits. When
38 either <since> or <until> is omitted, it defaults to
39 `HEAD`, i.e. the tip of the current branch.
40 For a more complete list of ways to spell <since>
41 and <until>, see "SPECIFYING REVISIONS" section in
42 linkgit:git-rev-parse[1].
43
44 --first-parent::
45 Follow only the first parent commit upon seeing a merge
46 commit. This option can give a better overview when
47 viewing the evolution of a particular topic branch,
48 because merges into a topic branch tend to be only about
49 adjusting to updated upstream from time to time, and
50 this option allows you to ignore the individual commits
51 brought in to your history by such a merge.
52
53 -g, \--walk-reflogs::
54 Show commits as they were recorded in the reflog. The log contains
55 a record about how the tip of a reference was changed.
56 Cannot be combined with --reverse.
57 See also linkgit:git-reflog[1].
58
59 --decorate::
60 Print out the ref names of any commits that are shown.
61
62 --full-diff::
63 Without this flag, "git log -p <paths>..." shows commits that
64 touch the specified paths, and diffs about the same specified
65 paths. With this, the full diff is shown for commits that touch
66 the specified paths; this means that "<paths>..." limits only
67 commits, and doesn't limit diff for those commits.
68
69 --follow::
70 Continue listing the history of a file beyond renames.
71
72 --log-size::
73 Before the log message print out its size in bytes. Intended
74 mainly for porcelain tools consumption. If git is unable to
75 produce a valid value size is set to zero.
76 Note that only message is considered, if also a diff is shown
77 its size is not included.
78
79 <paths>...::
80 Show only commits that affect the specified paths.
81
82
83 include::pretty-formats.txt[]
84
85 include::diff-generate-patch.txt[]
86
87 Examples
88 --------
89 git log --no-merges::
90
91 Show the whole commit history, but skip any merges
92
93 git log v2.6.12.. include/scsi drivers/scsi::
94
95 Show all commits since version 'v2.6.12' that changed any file
96 in the include/scsi or drivers/scsi subdirectories
97
98 git log --since="2 weeks ago" \-- gitk::
99
100 Show the changes during the last two weeks to the file 'gitk'.
101 The "--" is necessary to avoid confusion with the *branch* named
102 'gitk'
103
104 git log --name-status release..test::
105
106 Show the commits that are in the "test" branch but not yet
107 in the "release" branch, along with the list of paths
108 each commit modifies.
109
110 git log --follow builtin-rev-list.c::
111
112 Shows the commits that changed builtin-rev-list.c, including
113 those commits that occurred before the file was given its
114 present name.
115
116 Discussion
117 ----------
118
119 include::i18n.txt[]
120
121
122 Author
123 ------
124 Written by Linus Torvalds <torvalds@osdl.org>
125
126 Documentation
127 --------------
128 Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel.org>.
129
130 GIT
131 ---
132 Part of the linkgit:git[7] suite