Setup and Config
Getting and Creating Projects
Branching and Merging
Sharing and Updating Projects
Inspection and Comparison
- 2.0.2 → 2.0.3 no changes
- 2.0.1 06/25/14
- 2.0.0 05/28/14
- 1.9.3 → 1.9.4 no changes
- 1.9.2 04/09/14
- 1.9.1 no changes
- 1.9.0 02/14/14
- 126.96.36.199 → 188.8.131.52 no changes
- 184.108.40.206 12/17/13
- 220.127.116.11 no changes
- 1.8.5 11/27/13
- 18.104.22.168 → 22.214.171.124 no changes
- 1.8.4 08/23/13
- 126.96.36.199 07/22/13
- 188.8.131.52 07/15/13
- 184.108.40.206 no changes
- 220.127.116.11 06/10/13
- 1.8.3 05/24/13
- 18.104.22.168 no changes
- 22.214.171.124 04/26/13
- 126.96.36.199 04/07/13
- 188.8.131.52 04/07/13
- 184.108.40.206 → 220.127.116.11 no changes
- 1.8.1 12/31/12
- 18.104.22.168 12/27/12
- 22.214.171.124 → 126.96.36.199 no changes
- 1.8.0 10/21/12
- 188.8.131.52 → 184.108.40.206 no changes
- 220.127.116.11 09/30/12
- 18.104.22.168 09/18/12
- 1.7.12 08/20/12
- 22.214.171.124 no changes
- 126.96.36.199 09/11/12
- 188.8.131.52 08/15/12
- 184.108.40.206 → 220.127.116.11 no changes
- 18.104.22.168 07/11/12
- 22.214.171.124 → 126.96.36.199 no changes
- 188.8.131.52 05/25/12
- 184.108.40.206 → 220.127.116.11 no changes
- 1.7.10 04/06/12
- 18.104.22.168 → 22.214.171.124 no changes
- 126.96.36.199 03/12/12
- 188.8.131.52 03/05/12
- 184.108.40.206 → 220.127.116.11 no changes
- 1.7.9 01/27/12
- 18.104.22.168 04/26/12
- 22.214.171.124 → 126.96.36.199 no changes
- 1.7.8 12/02/11
- 188.8.131.52 04/26/12
- 184.108.40.206 → 220.127.116.11 no changes
- 18.104.22.168 11/09/11
- 22.214.171.124 no changes
- 126.96.36.199 10/24/11
- 1.7.7 09/30/11
- 188.8.131.52 → 184.108.40.206 no changes
- 220.127.116.11 09/12/11
- 18.104.22.168 09/06/11
- 22.214.171.124 08/24/11
- 1.7.6 06/26/11
- 126.96.36.199 no changes
- 188.8.131.52 05/26/11
- 184.108.40.206 05/20/11
- 220.127.116.11 05/04/11
- 1.7.5 04/24/11
- 18.104.22.168 04/19/11
- 22.214.171.124 04/06/11
- 126.96.36.199 no changes
- 188.8.131.52 03/26/11
- 184.108.40.206 no changes
- 1.7.4 01/31/11
git-log - Show commit logs
'git log' [<options>] [<revision range>] [[\--] <path>...]
Shows the commit logs.
The command takes options applicable to the
command to control what is shown and how, and options applicable to
git diff-* commands to control how the changes
each commit introduces are shown.
Continue listing the history of a file beyond renames (works only for a single file).
Print out the ref names of any commits that are shown. If short is specified, the ref name prefixes refs/heads/, refs/tags/ and refs/remotes/ will not be printed. If full is specified, the full ref name (including prefix) will be printed. The default option is short.
Print out the ref name given on the command line by which each commit was reached.
Use mailmap file to map author and committer names and email addresses to canonical real names and email addresses. See linkgit:git-shortlog.
Without this flag,
git log -p <path>...shows commits that touch the specified paths, and diffs about the same specified paths. With this, the full diff is shown for commits that touch the specified paths; this means that "<path>…" limits only commits, and doesn’t limit diff for those commits.
Note that this affects all diff-based output types, e.g. those produced by
Include a line “log size <number>” in the output for each commit, where <number> is the length of that commit’s message in bytes. Intended to speed up tools that read log messages from
git logoutput by allowing them to allocate space in advance.
- -L <start>,<end>:<file>
- -L :<regex>:<file>
Trace the evolution of the line range given by "<start>,<end>" (or the funcname regex <regex>) within the <file>. You may not give any pathspec limiters. This is currently limited to a walk starting from a single revision, i.e., you may only give zero or one positive revision arguments. You can specify this option more than once.
- <revision range>
Show only commits in the specified revision range. When no <revision range> is specified, it defaults to
HEAD(i.e. the whole history leading to the current commit).
origin..HEADspecifies all the commits reachable from the current commit (i.e.
HEAD), but not from
origin. For a complete list of ways to spell <revision range>, see the Specifying Ranges section of linkgit:gitrevisions.
- [\--] <path>…
Show only commits that are enough to explain how the files that match the specified paths came to be. See History Simplification below for details and other simplification modes.
Paths may need to be prefixed with ‘`-- '’ to separate them from options or the revision range, when confusion arises.
git log --no-merges
Show the whole commit history, but skip any merges
git log v2.6.12.. include/scsi drivers/scsi
Show all commits since version v2.6.12 that changed any file in the
git log --since="2 weeks ago" -- gitk
Show the changes during the last two weeks to the file gitk. The “--” is necessary to avoid confusion with the branch named gitk
git log --name-status release..test
Show the commits that are in the "test" branch but not yet in the "release" branch, along with the list of paths each commit modifies.
git log --follow builtin/rev-list.c
Shows the commits that changed
builtin/rev-list.c, including those commits that occurred before the file was given its present name.
git log --branches --not --remotes=origin
Shows all commits that are in any of local branches but not in any of remote-tracking branches for origin (what you have that origin doesn’t).
git log master --not --remotes=*/master
Shows all commits that are in local master but not in any remote repository master branches.
git log -p -m --first-parent
Shows the history including change diffs, but only from the “main branch” perspective, skipping commits that come from merged branches, and showing full diffs of changes introduced by the merges. This makes sense only when following a strict policy of merging all topic branches when staying on a single integration branch.
git log -L '/int main/',/^}/:main.c
Shows how the function
main()in the file
main.cevolved over time.
git log -3
Limits the number of commits to show to 3.
See linkgit:git-config for core variables and linkgit:git-diff for settings related to diff generation.
Default for the
--formatoption. (See Pretty Formats above.) Defaults to
Encoding to use when displaying logs. (See Discussion above.) Defaults to the value of
i18n.commitEncodingif set, and UTF-8 otherwise.
Default format for human-readable dates. (Compare the
--dateoption.) Defaults to "default", which means to write dates like
Sat May 8 19:35:34 2010 -0500.
git logand related commands will not treat the initial commit as a big creation event. Any root commits in
git log -poutput would be shown without a diff attached. The default is
Which refs, in addition to the default set by
core.notesRefor GIT_NOTES_REF, to read notes from when showing commit messages with the
logfamily of commands. See linkgit:git-notes.
May be an unabbreviated ref name or a glob and may be specified multiple times. A warning will be issued for refs that do not exist, but a glob that does not match any refs is silently ignored.
This setting can be disabled by the
--no-notesoption, overridden by the GIT_NOTES_DISPLAY_REF environment variable, and overridden by the
Part of the linkgit:git suite