<feed xmlns='http://www.w3.org/2005/Atom'>
<title>git/README.md, branch v2.22.2</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/git/git.git/
</subtitle>
<id>https://git.shady.money/git/atom?h=v2.22.2</id>
<link rel='self' href='https://git.shady.money/git/atom?h=v2.22.2'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/'/>
<updated>2019-07-18T21:47:46Z</updated>
<entry>
<title>README: fix rendering of text in angle brackets</title>
<updated>2019-07-18T21:47:46Z</updated>
<author>
<name>Doug Ilijev</name>
<email>doug.ilijev@gmail.com</email>
</author>
<published>2019-07-18T19:08:45Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=7926cee90466f3fcc3120b2d532c831474d5c2e7'/>
<id>urn:sha1:7926cee90466f3fcc3120b2d532c831474d5c2e7</id>
<content type='text'>
Markdown incorrectly interpreted `&lt;commandname&gt;` as an HTML tag;
use backticks to escape `Documentation/git-&lt;commandname&gt;.txt` to ensure
that it renders the text as intended.

Signed-off-by: Doug Ilijev &lt;doug.ilijev@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>README: adjust for final Azure Pipeline ID</title>
<updated>2019-02-24T05:27:04Z</updated>
<author>
<name>Johannes Schindelin</name>
<email>johannes.schindelin@gmx.de</email>
</author>
<published>2019-02-23T14:49:23Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=39ffebd23b1ef6830bf86043ef0b5c069d9299a9'/>
<id>urn:sha1:39ffebd23b1ef6830bf86043ef0b5c069d9299a9</id>
<content type='text'>
During the six months of development of the Azure Pipelines support, the
patches went through quite a few iterations of changes, and to test
those iterations, a temporary build definition was used.

In the meantime, Azure Pipelines support made it to `master`, and we now
have a regular Azure Pipeline, installed via the common GitHub App
workflow. This new pipeline has a different name (git.git instead of
test-git.git), and a new ID (11 instead of 2).

Let's adjust the badge in our README to reflect that final shape of the
Azure Pipeline.

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>README: add a build badge (status of the Azure Pipelines build)</title>
<updated>2019-01-29T17:26:47Z</updated>
<author>
<name>Johannes Schindelin</name>
<email>johannes.schindelin@gmx.de</email>
</author>
<published>2019-01-29T14:19:32Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=5f7864663bdb71635b4aaf0d996db14e4d521ff6'/>
<id>urn:sha1:5f7864663bdb71635b4aaf0d996db14e4d521ff6</id>
<content type='text'>
Just like so many other OSS projects, we now also have a build badge.

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>note git-security@googlegroups.com in more places</title>
<updated>2018-06-01T00:24:11Z</updated>
<author>
<name>Thomas Gummerer</name>
<email>t.gummerer@gmail.com</email>
</author>
<published>2018-05-30T20:52:55Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=2a00502b14cd88299c8e69abcedf8aadcfaaaa6e'/>
<id>urn:sha1:2a00502b14cd88299c8e69abcedf8aadcfaaaa6e</id>
<content type='text'>
Add a mention of the security mailing list to the README, and to
Documentation/SubmittingPatches..  2caa7b8d27 ("git manpage: note
git-security@googlegroups.com", 2018-03-08) already added it to the
man page, but for developers either the README, or the documentation
on how to contribute (SubmittingPatches) may be the first place to
look.

Use the same wording as we already have on the git-scm.com website and
in the man page for the README, while the wording is adjusted in
SubmittingPatches to match the surrounding document better.

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>README: create HTTP/HTTPS links from URLs in Markdown</title>
<updated>2017-03-01T22:45:45Z</updated>
<author>
<name>Eric Wong</name>
<email>e@80x24.org</email>
</author>
<published>2017-03-01T22:22:04Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=bcd886d897d22f88fac63fd190b65884f4c58f8f'/>
<id>urn:sha1:bcd886d897d22f88fac63fd190b65884f4c58f8f</id>
<content type='text'>
Markdown supports automatic links by surrounding URLs with
angle brackets, as documented in
&lt;https://daringfireball.net/projects/markdown/syntax#autolink&gt;

While we're at it, update URLs to avoid redirecting clients for
git-scm.com (by using HTTPS) and public-inbox.org (by adding a
trailing slash).

Signed-off-by: Eric Wong &lt;e@80x24.org&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>README: replace gmane link with public-inbox</title>
<updated>2016-12-15T17:30:09Z</updated>
<author>
<name>Jeff King</name>
<email>peff@peff.net</email>
</author>
<published>2016-12-15T14:17:19Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=54471fdcc3acf26946258a0f1a4583b1964e47f2'/>
<id>urn:sha1:54471fdcc3acf26946258a0f1a4583b1964e47f2</id>
<content type='text'>
The general status and future of gmane is unclear at this
point, but certainly it does not seem to be carrying
gmane.comp.version-control.git at all anymore. Let's point
to public-inbox.org, which seems to be the favored archive
on the list these days (and which uses message-ids in its
URLs, making the links somewhat future-proof).

Reported-by: Chiel ten Brinke &lt;ctenbrinke@gmail.com&gt;
Signed-off-by: Jeff King &lt;peff@peff.net&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>README.md: format CLI commands with code syntax</title>
<updated>2016-05-31T15:54:24Z</updated>
<author>
<name>Benjamin Dopplinger</name>
<email>b.dopplinger@gmail.com</email>
</author>
<published>2016-05-30T03:08:16Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=a299e3a39619dc5e05790d0cc06d8336e7c3d756'/>
<id>urn:sha1:a299e3a39619dc5e05790d0cc06d8336e7c3d756</id>
<content type='text'>
CLI commands which are mentioned in the readme are now formatted with
the Markdown code syntax to make the documentation more readable.

Signed-off-by: Benjamin Dopplinger &lt;b.dopplinger@gmail.com&gt;
Reviewed-by: Matthieu Moy &lt;Matthieu.Moy@imag.fr&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>README.md: don't take 'commandname' literally</title>
<updated>2016-04-03T17:12:48Z</updated>
<author>
<name>Matthieu Moy</name>
<email>Matthieu.Moy@imag.fr</email>
</author>
<published>2016-02-27T10:46:12Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=c9a014e38e5e2c2fb73b2e971705b320d517c65c'/>
<id>urn:sha1:c9a014e38e5e2c2fb73b2e971705b320d517c65c</id>
<content type='text'>
The link to Documentation/git-commandname.txt was obviously broken.
Remove the link and make it clear that it is not a literal path name by
using *italics* in makdown.

Signed-off-by: Matthieu Moy &lt;Matthieu.Moy@imag.fr&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>README.md: move down historical explanation about the name</title>
<updated>2016-02-25T17:33:58Z</updated>
<author>
<name>Matthieu Moy</name>
<email>Matthieu.Moy@imag.fr</email>
</author>
<published>2016-02-25T08:37:30Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=a217f07388b847192565c71e5ef6a9cc81633594'/>
<id>urn:sha1:a217f07388b847192565c71e5ef6a9cc81633594</id>
<content type='text'>
The explanations about why the name was chosen are secondary compared to
the description and link to the documentation.

Some consider these explanations as good computer scientists joke, but
other see it as needlessly offensive vocabulary.

This patch preserves the historical joke, but gives it less importance
by moving it to the end of the README, and makes it clear that it is a
historical explanation, that does not necessarily reflect the state of
mind of current developers.

Signed-off-by: Matthieu Moy &lt;Matthieu.Moy@imag.fr&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>README.md: don't call git stupid in the title</title>
<updated>2016-02-25T17:33:58Z</updated>
<author>
<name>Matthieu Moy</name>
<email>Matthieu.Moy@imag.fr</email>
</author>
<published>2016-02-25T08:37:29Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=28513c4f56a2164fd6d3a16ceddbab3a5bf3f191'/>
<id>urn:sha1:28513c4f56a2164fd6d3a16ceddbab3a5bf3f191</id>
<content type='text'>
"the stupid content tracker" was true in the early days of Git, but
hardly applicable these days. "fast, scalable, distributed" describes
Git more accuralety.

Also, "stupid" can be seen as offensive by some people. Let's not use it
in the very first words of the README.

The new formulation is taken from the description of the Debian package.

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