|
|
|
|
git-whatchanged(1)
|
|
|
|
|
==================
|
|
|
|
|
|
|
|
|
|
NAME
|
|
|
|
|
----
|
|
|
|
|
git-whatchanged - Show logs with difference each commit introduces
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
SYNOPSIS
|
|
|
|
|
--------
|
|
|
|
|
[verse]
|
|
|
|
|
'git 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.
|
|
|
|
|
|
|
|
|
|
include::pretty-options.txt[]
|
|
|
|
|
|
|
|
|
|
include::pretty-formats.txt[]
|
|
|
|
|
|
|
|
|
|
Examples
|
|
|
|
|
--------
|
docs: put listed example commands in backticks
Many examples of git command invocation are given in asciidoc listing
blocks, which makes them monospaced and avoids further interpretation of
special characters. Some manpages make a list of examples, like:
git foo::
Run git foo.
git foo -q::
Use the "-q" option.
to quickly show many variants. However, they can sometimes be hard to
read, because they are shown in a proportional-width font (so, for
example, seeing the difference between "-- foo" and "--foo" can be
difficult).
This patch puts all such examples into backticks, which gives the
equivalent formatting to a listing block (i.e., monospaced and without
character interpretation).
As a bonus, this also fixes an example in the git-push manpage, in which
"git push origin :::" was accidentally considered a newly-indented list,
and not a list item with "git push origin :" in it.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
13 years ago
|
|
|
`git 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
|
|
|
|
|
|
docs: stop using asciidoc no-inline-literal
In asciidoc 7, backticks like `foo` produced a typographic
effect, but did not otherwise affect the syntax. In asciidoc
8, backticks introduce an "inline literal" inside which markup
is not interpreted. To keep compatibility with existing
documents, asciidoc 8 has a "no-inline-literal" attribute to
keep the old behavior. We enabled this so that the
documentation could be built on either version.
It has been several years now, and asciidoc 7 is no longer
in wide use. We can now decide whether or not we want
inline literals on their own merits, which are:
1. The source is much easier to read when the literal
contains punctuation. You can use `master~1` instead
of `master{tilde}1`.
2. They are less error-prone. Because of point (1), we
tend to make mistakes and forget the extra layer of
quoting.
This patch removes the no-inline-literal attribute from the
Makefile and converts every use of backticks in the
documentation to an inline literal (they must be cleaned up,
or the example above would literally show "{tilde}" in the
output).
Problematic sites were found by grepping for '`.*[{\\]' and
examined and fixed manually. The results were then verified
by comparing the output of "html2text" on the set of
generated html pages. Doing so revealed that in addition to
making the source more readable, this patch fixes several
formatting bugs:
- HTML rendering used the ellipsis character instead of
literal "..." in code examples (like "git log A...B")
- some code examples used the right-arrow character
instead of '->' because they failed to quote
- api-config.txt did not quote tilde, and the resulting
HTML contained a bogus snippet like:
<tt><sub></tt> foo <tt></sub>bar</tt>
which caused some parsers to choke and omit whole
sections of the page.
- git-commit.txt confused ``foo`` (backticks inside a
literal) with ``foo'' (matched double-quotes)
- mentions of `A U Thor <author@example.com>` used to
erroneously auto-generate a mailto footnote for
author@example.com
- the description of --word-diff=plain incorrectly showed
the output as "[-removed-] and {added}", not "{+added+}".
- using "prime" notation like:
commit `C` and its replacement `C'`
confused asciidoc into thinking that everything between
the first backtick and the final apostrophe were meant
to be inside matched quotes
- asciidoc got confused by the escaping of some of our
asterisks. In particular,
`credential.\*` and `credential.<url>.\*`
properly escaped the asterisk in the first case, but
literally passed through the backslash in the second
case.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
13 years ago
|
|
|
`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'
|
|
|
|
|
|
|
|
|
|
GIT
|
|
|
|
|
---
|
|
|
|
|
Part of the linkgit:git[1] suite
|
