<feed xmlns='http://www.w3.org/2005/Atom'>
<title>git/Documentation/diff-options.txt, branch v2.9.2</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/git/git.git/
</subtitle>
<id>https://git.shady.money/git/atom?h=v2.9.2</id>
<link rel='self' href='https://git.shady.money/git/atom?h=v2.9.2'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/'/>
<updated>2016-06-10T22:26:06Z</updated>
<entry>
<title>Merge branch 'jk/diff-compact-heuristic'</title>
<updated>2016-06-10T22:26:06Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2016-06-10T22:26:06Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=e5f767554404592cf65e7c49b3594b195a324031'/>
<id>urn:sha1:e5f767554404592cf65e7c49b3594b195a324031</id>
<content type='text'>
It turns out that the earlier effort to update the heuristics may
want to use a bit more time to mature.  Turn it off by default.

* jk/diff-compact-heuristic:
  diff: disable compaction heuristic for now
</content>
</entry>
<entry>
<title>diff: disable compaction heuristic for now</title>
<updated>2016-06-10T20:45:23Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2016-06-10T17:58:55Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=5580b271af518bae30148edfd42cc8459d8da384'/>
<id>urn:sha1:5580b271af518bae30148edfd42cc8459d8da384</id>
<content type='text'>
http://lkml.kernel.org/g/20160610075043.GA13411@sigill.intra.peff.net
reports that a change to add a new "function" with common ending
with the existing one at the end of the file is shown like this:

    def foo
      do_foo_stuff()

   +  common_ending()
   +end
   +
   +def bar
   +  do_bar_stuff()
   +
      common_ending()
    end

when the new heuristic is in use.  In reality, the change is to add
the blank line before "def bar" and everything below, which is what
the code without the new heuristic shows.

Disable the heuristics by default, and resurrect the documentation
for the option and the configuration variables, while clearly
marking the feature as still experimental.

Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Documentation: fix linkgit references</title>
<updated>2016-05-09T22:44:14Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2016-05-04T17:36:24Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=1cca17dfff488760e74e2af4b0f686b20a02e6e1'/>
<id>urn:sha1:1cca17dfff488760e74e2af4b0f686b20a02e6e1</id>
<content type='text'>
There are a handful of incorrect "linkgit:&lt;page&gt;[&lt;section&gt;]"
instances in our documentation set.

 * Some have an extra colon after "linkgit:"; fix them by removing
   the extra colon;

 * Some refer to a page outside the Git suite, namely curl(1); fix
   them by using the `curl(1)` that already appears on the same page
   for the same purpose of referring the readers to its manual page.

 * Some spell the name of the page incorrectly, e.g. "rev-list" when
   they mean "git-rev-list"; fix them.

 * Some list the manual section incorrectly; fix them to make sure
   they match what is at the top of the target of the link.

Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'es/format-patch-doc-hide-no-patch' into maint</title>
<updated>2016-05-02T21:24:06Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2016-05-02T21:24:06Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=a3fa5653276ed923ef079188459242f3f7e6264d'/>
<id>urn:sha1:a3fa5653276ed923ef079188459242f3f7e6264d</id>
<content type='text'>
"git format-patch --help" showed `-s` and `--no-patch` as if these
are valid options to the command.  We already hide `--patch` option
from the documentation, because format-patch is about showing the
diff, and the documentation now hides these options as well.

* es/format-patch-doc-hide-no-patch:
  git-format-patch.txt: don't show -s as shorthand for multiple options
</content>
</entry>
<entry>
<title>diff: undocument the compaction heuristic knobs for experimentation</title>
<updated>2016-05-02T17:36:36Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2016-05-02T17:36:36Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=77085a616b0fe0eaba99dfe27247ae733f1570e9'/>
<id>urn:sha1:77085a616b0fe0eaba99dfe27247ae733f1570e9</id>
<content type='text'>
It seems that people around here are all happy with the updated
heuristics used to decide where the hunks are separated.  Let's keep
that as the default.  Even though we do not expect too much trouble
from the difference between the old and the new algorithms, just in
case let's leave the implementation of the knobs to turn it off for
emergencies.  There is no longer need for documenting them, though.

Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>xdiff: implement empty line chunk heuristic</title>
<updated>2016-04-19T17:53:34Z</updated>
<author>
<name>Stefan Beller</name>
<email>sbeller@google.com</email>
</author>
<published>2016-04-19T15:21:30Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=d634d61ed6c5f19948937012b5e3a0ed2d631d3f'/>
<id>urn:sha1:d634d61ed6c5f19948937012b5e3a0ed2d631d3f</id>
<content type='text'>
In order to produce the smallest possible diff and combine several diff
hunks together, we implement a heuristic from GNU Diff which moves diff
hunks forward as far as possible when we find common context above and
below a diff hunk. This sometimes produces less readable diffs when
writing C, Shell, or other programming languages, ie:

...
 /*
+ *
+ *
+ */
+
+/*
...

instead of the more readable equivalent of

...
+/*
+ *
+ *
+ */
+
 /*
...

Implement the following heuristic to (optionally) produce the desired
output.

  If there are diff chunks which can be shifted around, shift each hunk
  such that the last common empty line is below the chunk with the rest
  of the context above.

This heuristic appears to resolve the above example and several other
common issues without producing significantly weird results. However, as
with any heuristic it is not really known whether this will always be
more optimal. Thus, it can be disabled via diff.compactionHeuristic.

Signed-off-by: Stefan Beller &lt;sbeller@google.com&gt;
Signed-off-by: Jacob Keller &lt;jacob.e.keller@intel.com&gt;
Signed-off-by: Stefan Beller &lt;sbeller@google.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>git-format-patch.txt: don't show -s as shorthand for multiple options</title>
<updated>2016-04-04T20:46:54Z</updated>
<author>
<name>Eric Sunshine</name>
<email>sunshine@sunshineco.com</email>
</author>
<published>2016-03-27T21:26:07Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=b73a1bcc1a9f9290bdc024c816d6c41b353c5eab'/>
<id>urn:sha1:b73a1bcc1a9f9290bdc024c816d6c41b353c5eab</id>
<content type='text'>
git-format-patch recognizes -s as shorthand only for --signoff, however,
its documentation shows -s as shorthand for both --signoff and
--no-patch. Resolve this confusion by suppressing the bogus -s shorthand
for --no-patch.

While here, also avoid showing the --no-patch option in git-format-patch
documentation since it doesn't make sense to ask to suppress the patch
while at the same time explicitly asking to format the patch (which,
after all, is the purpose of git-format-patch).

Reported-by: Kevin Brodsky &lt;corax26@gmail.com&gt;
Signed-off-by: Eric Sunshine &lt;sunshine@sunshineco.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Documentation: git diff --check detects conflict markers</title>
<updated>2016-03-29T20:14:50Z</updated>
<author>
<name>Ori Avtalion</name>
<email>ori@avtalion.name</email>
</author>
<published>2016-03-29T18:59:45Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=30211fb68d64c2b3852da5b5f846d8d52d70c9c1'/>
<id>urn:sha1:30211fb68d64c2b3852da5b5f846d8d52d70c9c1</id>
<content type='text'>
Signed-off-by: Ori Avtalion &lt;ori@avtalion.name&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Documentation/diff: give --word-diff-regex=. example</title>
<updated>2015-11-24T23:38:46Z</updated>
<author>
<name>Michael J Gruber</name>
<email>git@drmicha.warpmail.net</email>
</author>
<published>2015-11-20T13:36:14Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=2c15c006511e03e775fa5f2e44b37ae9313833b0'/>
<id>urn:sha1:2c15c006511e03e775fa5f2e44b37ae9313833b0</id>
<content type='text'>
It's just so useful.

Signed-off-by: Michael J Gruber &lt;git@drmicha.warpmail.net&gt;
Signed-off-by: Jeff King &lt;peff@peff.net&gt;
</content>
</entry>
<entry>
<title>Merge branch 'mm/log-format-raw-doc' into maint</title>
<updated>2015-06-16T21:33:43Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2015-06-16T21:33:42Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=4be33f7222990c1c761cd1c497c0db88b3d376cc'/>
<id>urn:sha1:4be33f7222990c1c761cd1c497c0db88b3d376cc</id>
<content type='text'>
Clarify that "log --raw" and "log --format=raw" are unrelated
concepts.

* mm/log-format-raw-doc:
  Documentation/log: clarify sha1 non-abbreviation in log --raw
  Documentation/log: clarify what --raw means
</content>
</entry>
</feed>
