<feed xmlns='http://www.w3.org/2005/Atom'>
<title>git/.gitattributes, branch v2.45.2</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/git/git.git/
</subtitle>
<id>https://git.shady.money/git/atom?h=v2.45.2</id>
<link rel='self' href='https://git.shady.money/git/atom?h=v2.45.2'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/'/>
<updated>2023-02-06T21:57:08Z</updated>
<entry>
<title>.gitattributes: include `text` attribute for eol attributes</title>
<updated>2023-02-06T21:57:08Z</updated>
<author>
<name>Philip Oakley</name>
<email>philipoakley@iee.email</email>
</author>
<published>2023-02-03T12:59:20Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=1f34e0cd3d799acb5118b3276dde389821bffdd4'/>
<id>urn:sha1:1f34e0cd3d799acb5118b3276dde389821bffdd4</id>
<content type='text'>
The standard advice for text file eol endings in the .gitattributes file
was updated in e28eae3184 (gitattributes: Document the unified "auto"
handling, 2016-08-26) with a recent clarification in 8c591dbfce (docs:
correct documentation about eol attribute, 2022-01-11), with a follow
up comment by the original author in [1] confirming the use of the eol
attribute in conjunction with the text attribute.

Update Git's .gitattributes file to reflect our own advice.

[1] https://lore.kernel.org/git/?q=%3C20220216115239.uo2ie3flaqo3nf2d%40tb-raspi4%3E.

Signed-off-by: Philip Oakley &lt;philipoakley@iee.email&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>CoC: explicitly take any whitespace breakage</title>
<updated>2021-01-04T17:44:49Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2021-01-04T17:43:31Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=ffd27e6cb24c6f4a34204cbfbb26e6612689d1f4'/>
<id>urn:sha1:ffd27e6cb24c6f4a34204cbfbb26e6612689d1f4</id>
<content type='text'>
We'll keep this document mostly in sync with the upstream; let's
help "git am" and "git show" by telling them that they may introduce
what we may consider whitespace errors.

Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Mark .bat files as requiring CR/LF endings</title>
<updated>2019-06-20T21:03:05Z</updated>
<author>
<name>Johannes Schindelin</name>
<email>johannes.schindelin@gmx.de</email>
</author>
<published>2019-06-19T21:05:57Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=a5bdf9fdf1f6fe566f206097df321f28fe1593e3'/>
<id>urn:sha1:a5bdf9fdf1f6fe566f206097df321f28fe1593e3</id>
<content type='text'>
Just like the natural line ending for Unix shell scripts consist of a
single Line Feed, the natural line ending for (DOS) Batch scripts
consists of a Carriage Return followed by a Line Feed.

It seems that both Unix shell script interpreters and the interpreter
for Batch scripts (`cmd.exe`) are keen on seeing the "right" line
endings.

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>Merge branch 'ds/hash-independent-tests-fix' into maint</title>
<updated>2018-12-15T03:24:32Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2018-12-15T03:24:32Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=3f8c27c369833ac0eb473cadbec8c9deb0ee311b'/>
<id>urn:sha1:3f8c27c369833ac0eb473cadbec8c9deb0ee311b</id>
<content type='text'>
Test portability fix.

* ds/hash-independent-tests-fix:
  .gitattributes: ensure t/oid-info/* has eol=lf
</content>
</entry>
<entry>
<title>.gitattributes: ensure t/oid-info/* has eol=lf</title>
<updated>2018-12-14T03:53:06Z</updated>
<author>
<name>Derrick Stolee</name>
<email>dstolee@microsoft.com</email>
</author>
<published>2018-12-11T20:35:46Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=fc767afe77ee0e1bca50d86c8ec1277ea473b1bc'/>
<id>urn:sha1:fc767afe77ee0e1bca50d86c8ec1277ea473b1bc</id>
<content type='text'>
The new test_oid machinery in the test library requires reading
some information from t/oid-info/hash-info and t/oid-info/oid.

The logic to read from these files in shell uses built-in "read"
command, which leaves CR at the end of these text files when they
are checked out with CRLF line endings, at least when run with bash
shipped with Git for Windows.  This results in an unexpected value
in the variable these lines are read into, leading the tests to
fail.

Mark them to be checked out always with the LF line endings.

Signed-off-by: Derrick Stolee &lt;dstolee@microsoft.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>build: fix broken command-list.h generation with core.autocrlf</title>
<updated>2018-11-12T07:39:17Z</updated>
<author>
<name>Nguyễn Thái Ngọc Duy</name>
<email>pclouds@gmail.com</email>
</author>
<published>2018-11-10T18:23:23Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=54709d520466d6e1d2feab6499a3fc6bf348e32a'/>
<id>urn:sha1:54709d520466d6e1d2feab6499a3fc6bf348e32a</id>
<content type='text'>
The script generate-cmdlist.sh needs input text files in UNIX line
ending to work correctly. It's been fine even with core.autocrlf set
because Documentation/git-*.txt is forced LF conversion.

But this leaves out gitk.txt and also Documentation/*config.txt that
recently becomes new input for this script. Update the attribute file
to force LF on all *.txt files to be on the safe side.

For more details, please see 00ddc9d13c (Fix build with
core.autocrlf=true - 2017-05-09)

Signed-off-by: Nguyễn Thái Ngọc Duy &lt;pclouds@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>.gitattributes: add conflict-marker-size for relevant files</title>
<updated>2018-08-29T18:27:31Z</updated>
<author>
<name>Thomas Gummerer</name>
<email>t.gummerer@gmail.com</email>
</author>
<published>2018-08-28T22:05:50Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=b9b07efdb2ac35684d3ee3fe98f91691d5b8642a'/>
<id>urn:sha1:b9b07efdb2ac35684d3ee3fe98f91691d5b8642a</id>
<content type='text'>
Some files in git.git contain lines that look like conflict markers,
either in examples or tests, or in the case of Documentation/gitk.txt
because of the asciidoc heading.

Having conflict markers the same length as the actual content can be
confusing for humans, and is impossible to handle for tools like 'git
rerere'.  Work around that by setting the 'conflict-marker-size'
attribute for those files to 32, which makes the conflict markers
unambiguous.

Helped-by: Junio C Hamano &lt;gitster@pobox.com&gt;
Signed-off-by: Thomas Gummerer &lt;t.gummerer@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>.gitattributes: add a diff driver for Python</title>
<updated>2018-04-27T00:18:55Z</updated>
<author>
<name>Ævar Arnfjörð Bjarmason</name>
<email>avarab@gmail.com</email>
</author>
<published>2018-04-26T07:50:58Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=7818b619e2c88eecd6410286f67c944f3d0d9caa'/>
<id>urn:sha1:7818b619e2c88eecd6410286f67c944f3d0d9caa</id>
<content type='text'>
Declare that the *.py files in our tree are Python for the purposes of
diffing, and as in 00ddc9d13c ("Fix build with core.autocrlf=true",
2017-05-09) set eol=lf on them, which makes sense like with the *.perl
files.

Signed-off-by: Ævar Arnfjörð Bjarmason &lt;avarab@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>.gitattributes: use the "perl" differ for Perl</title>
<updated>2018-04-27T00:18:55Z</updated>
<author>
<name>Ævar Arnfjörð Bjarmason</name>
<email>avarab@gmail.com</email>
</author>
<published>2018-04-26T07:50:57Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=20460635a864c2d9256339864a724a0f2e9a5ea7'/>
<id>urn:sha1:20460635a864c2d9256339864a724a0f2e9a5ea7</id>
<content type='text'>
As noted in gitattributes(5) this gives better patch context for these
types of files.

Signed-off-by: Ævar Arnfjörð Bjarmason &lt;avarab@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>.gitattributes: add *.pl extension for Perl</title>
<updated>2018-04-27T00:18:55Z</updated>
<author>
<name>Ævar Arnfjörð Bjarmason</name>
<email>avarab@gmail.com</email>
</author>
<published>2018-04-26T07:50:56Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=00acdbc6fd5aa1635cf0a6dfa8a4c44e9b75e09e'/>
<id>urn:sha1:00acdbc6fd5aa1635cf0a6dfa8a4c44e9b75e09e</id>
<content type='text'>
Change the list of Perl extensions added in 00ddc9d13c ("Fix build
with core.autocrlf=true", 2017-05-09) to also include *.pl, we have
some of those in the tree, e.g. in t/.

Signed-off-by: Ævar Arnfjörð Bjarmason &lt;avarab@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
</feed>
