<feed xmlns='http://www.w3.org/2005/Atom'>
<title>git/t/t4013/diff.show_-c_master, branch master</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/git/git.git/
</subtitle>
<id>https://git.shady.money/git/atom?h=master</id>
<link rel='self' href='https://git.shady.money/git/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/'/>
<updated>2025-09-10T20:34:59Z</updated>
<entry>
<title>t4013: switch default branch name to main</title>
<updated>2025-09-10T20:34:59Z</updated>
<author>
<name>Phillip Wood</name>
<email>phillip.wood@dunelm.org.uk</email>
</author>
<published>2025-09-10T15:29:01Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=877176e0b01ea6aff551fa80734116a45748c6a3'/>
<id>urn:sha1:877176e0b01ea6aff551fa80734116a45748c6a3</id>
<content type='text'>
Remove one of the last remaining uses of
"TEST_GIT_DEFAULT_INITIAL_BRANCH= main" in the test suite. We have
been steadily be converting tests from using "master" as the default
branch name since the introduction of TEST_GIT_DEFAULT_INITIAL_BRANCH
in 704fed9ea22 (tests: start moving to a different default main branch
name, 2020-10-23) The changes here are purely mechanical replacing
"master" with "main"

Signed-off-by: Phillip Wood &lt;phillip.wood@dunelm.org.uk&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Revert "fmt-merge-msg: stop treating `master` specially"</title>
<updated>2020-07-30T19:41:49Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2020-07-30T17:06:42Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=21531927e4e1b9fdf524983414ee59558cb4f3d6'/>
<id>urn:sha1:21531927e4e1b9fdf524983414ee59558cb4f3d6</id>
<content type='text'>
This reverts commit 489947cee5095b168cbac111ff7bd1eadbbd90dd, which
stopped treating merges into the 'master' branch as special when
preparing the default merge message.  As the goal was not to have
any single branch designated as special, it solved it by leaving the
"into &lt;branchname&gt;" at the end of the title of the default merge
message for any and all branches.  An obvious and easy alternative
to treat everybody equally could have been to remove it for every
branch, but that involves loss of information.

We'll introduce a new mechanism to let end-users specify merges into
which branches would omit the "into &lt;branchname&gt;" from the title of
the default merge message, and make the mechanism, when unconfigured,
treat the traditional 'master' special again, so all the changes to
the tests we made earlier will become unnecessary, as these tests
will be run without configuring the said new mechanism.

Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>fmt-merge-msg: stop treating `master` specially</title>
<updated>2020-06-24T00:22:35Z</updated>
<author>
<name>Johannes Schindelin</name>
<email>johannes.schindelin@gmx.de</email>
</author>
<published>2020-06-23T22:33:23Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=489947cee5095b168cbac111ff7bd1eadbbd90dd'/>
<id>urn:sha1:489947cee5095b168cbac111ff7bd1eadbbd90dd</id>
<content type='text'>
In the context of many projects renaming their primary branch names away
from `master`, Git wants to stop treating the `master` branch specially.

Let's start with `git fmt-merge-msg`.

Signed-off-by: Johannes Schindelin &lt;johannes.schindelin@gmx.de&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>show -c: show patch text</title>
<updated>2010-03-09T09:11:18Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2010-03-09T07:27:25Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=b44900599710c700c1bf164d3753eb7f8eb6c18a'/>
<id>urn:sha1:b44900599710c700c1bf164d3753eb7f8eb6c18a</id>
<content type='text'>
Traditionally, "show" defaulted to "show --cc" (dense combined patch), but
asking for combined patch with "show -c" didn't turn the patch output
format on; the placement of this logic in setup_revisions() dates back to
cd2bdc5 (Common option parsing for "git log --diff" and friends,
2006-04-14).

This unfortunately cannot be done as a trivial change of "if dense
combined is asked, default to patch format" done in setup_revisions() to
"if any combined is asked, default to patch format", as "diff-tree -c"
needs to default to raw, while "diff-tree --cc" needs to default to patch,
and they share the codepath.  These command specific defaults are now
handled in the new "tweak" callback that can be customized by individual
command implementations.

Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
</feed>
