GIT-WHATCHANGED(1) Git Manual GIT-WHATCHANGED(1)NAMEgit-whatchanged - Show logs with difference each commit introduces
SYNOPSISgit-whatchanged <option>...
DESCRIPTION
Shows commit logs and diff output each commit introduces. The command
internally invokes git-rev-list piped to git-diff-tree, and takes
command line options for both of these commands.
This manual page describes only the most frequently used options.
OPTIONS-p Show textual diffs, instead of the git internal diff output
format that is useful only to tell the changed paths and their
nature of changes.
-<n> Limit output to <n> commits.
<since>..<until>
Limit output to between the two named commits (bottom exclusive,
top inclusive).
-r Show git internal diff output, but for the whole tree, not just
the top level.
-m By default, differences for merge commits are not shown. With
this flag, show differences to that commit from all of its
parents.
However, it is not very useful in general, although it is useful
on a file-by-file basis.
--pretty[=<format>]
Pretty-print the contents of the commit logs in a given format,
where <format> can be one of oneline, short, medium, full,
fuller, email, raw and format:<string>. When omitted, the format
defaults to medium.
Note: you can specify the default pretty format in the
repository configuration (see git-config(1)).
--abbrev-commit
Instead of showing the full 40-byte hexadecimal commit object
name, show only handful hexdigits prefix. Non default number of
digits can be specified with "--abbrev=<n>" (which also modifies
diff output, if it is displayed).
This should make "--pretty=oneline" a whole lot more readable
for people using 80-column terminals.
--encoding[=<encoding>]
The commit objects record the encoding used for the log message
in their encoding header; this option can be used to tell the
command to re-code the commit log message in the encoding
preferred by the user. For non plumbing commands this defaults
to UTF-8.
PRETTY FORMATS
If the commit is a merge, and if the pretty-format is not oneline,
email or raw, an additional line is inserted before the Author: line.
This line begins with "Merge: " and the sha1s of ancestral commits are
printed, separated by spaces. Note that the listed commits may not
necessarily be the list of the direct parent commits if you have
limited your view of history: for example, if you are only interested
in changes related to a certain directory or file.
Here are some additional details for each format:
· oneline
<sha1> <title line>
This is designed to be as compact as possible.
· short
commit <sha1>
Author: <author>
<title line>
· medium
commit <sha1>
Author: <author>
Date: <date>
<title line>
<full commit message>
· full
commit <sha1>
Author: <author>
Commit: <committer>
<title line>
<full commit message>
· fuller
commit <sha1>
Author: <author>
AuthorDate: <date & time>
Commit: <committer>
CommitDate: <date & time>
<title line>
<full commit message>
· email
From <sha1> <date>
From: <author>
Date: <date & time>
Subject: [PATCH] <title line>
<full commit message>
· raw
The raw format shows the entire commit exactly as stored in the
commit object. Notably, the SHA1s are displayed in full, regardless
of whether --abbrev or --no-abbrev are used, and parents information
show the true parent commits, without taking grafts nor history
simplification into account.
· format:
The format: format allows you to specify which information you want
to show. It works a little bit like printf format, with the notable
exception that you get a newline with %n instead of \n.
E.g, format:"The author of %h was %an, %ar%nThe title was >>%s<<%n"
would show something like this:
The author of fe6e0ee was Junio C Hamano, 23 hours ago
The title was >>t4119: test autocomputing -p<n> for traditional diff input.<<
The placeholders are:
· %H: commit hash
· %h: abbreviated commit hash
· %T: tree hash
· %t: abbreviated tree hash
· %P: parent hashes
· %p: abbreviated parent hashes
· %an: author name
· %ae: author email
· %ad: author date
· %aD: author date, RFC2822 style
· %ar: author date, relative
· %at: author date, UNIX timestamp
· %ai: author date, ISO 8601 format
· %cn: committer name
· %ce: committer email
· %cd: committer date
· %cD: committer date, RFC2822 style
· %cr: committer date, relative
· %ct: committer date, UNIX timestamp
· %ci: committer date, ISO 8601 format
· %e: encoding
· %s: subject
· %b: body
· %Cred: switch color to red
· %Cgreen: switch color to green
· %Cblue: switch color to blue
· %Creset: reset color
· %m: left, right or boundary mark
· %n: newline
EXAMPLESgit-whatchanged-p v2.6.12.. include/scsi drivers/scsi
Show as patches the commits since version v2.6.12 that changed
any file in the include/scsi or drivers/scsi subdirectories
git-whatchanged --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
AUTHOR
Written by Linus Torvalds <torvalds@osdl.org> and Junio C Hamano
<junkio@cox.net>
DOCUMENTATION
Documentation by David Greaves, Junio C Hamano and the git-list
<git@vger.kernel.org>.
GIT
Part of the git(7) suite
Git 1.5.5.2 10/21/2008 GIT-WHATCHANGED(1)
