<feed xmlns='http://www.w3.org/2005/Atom'>
<title>git/Documentation/MyFirstContribution.txt, branch v2.42.2</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/git/git.git/
</subtitle>
<id>https://git.shady.money/git/atom?h=v2.42.2</id>
<link rel='self' href='https://git.shady.money/git/atom?h=v2.42.2'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/'/>
<updated>2023-08-04T17:52:31Z</updated>
<entry>
<title>Merge branch 'jc/doc-sent-patch-now-what'</title>
<updated>2023-08-04T17:52:31Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2023-08-04T17:52:30Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=23b20fff3ab28b31678d23e67de328ac24801f18'/>
<id>urn:sha1:23b20fff3ab28b31678d23e67de328ac24801f18</id>
<content type='text'>
Process document update.

* jc/doc-sent-patch-now-what:
  MyFirstContribution: refrain from self-iterating too much
</content>
</entry>
<entry>
<title>MyFirstContribution: refrain from self-iterating too much</title>
<updated>2023-07-28T00:44:07Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2023-07-28T00:43:17Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=010447cf098f7407008f2940b4fefa5351477044'/>
<id>urn:sha1:010447cf098f7407008f2940b4fefa5351477044</id>
<content type='text'>
Finding mistakes in and improving your own patches is a good idea,
but doing so too quickly is being inconsiderate to reviewers who
have just seen the initial iteration and taking their time to review
it.  Encourage new developers to perform such a self review before
they send out their patches, not after.  After sending a patch that
they immediately found mistakes in, they are welcome to comment on
them, mentioning what and how they plan to improve them in an
updated version, before sending out their updates.

Helped-by: Torsten Bögershausen &lt;tboegi@web.de&gt;
Helped-by: Linus Arver &lt;linusa@google.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'la/mfc-markup-fix'</title>
<updated>2023-04-18T01:05:12Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2023-04-18T01:05:12Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=953823fcbf7da6eee4a3bd20690d2f1ff51365d5'/>
<id>urn:sha1:953823fcbf7da6eee4a3bd20690d2f1ff51365d5</id>
<content type='text'>
Documentation mark-up fix.

* la/mfc-markup-fix:
  MyFirstContribution: render literal *
</content>
</entry>
<entry>
<title>MyFirstContribution: render literal *</title>
<updated>2023-04-06T22:03:18Z</updated>
<author>
<name>Linus Arver</name>
<email>linusa@google.com</email>
</author>
<published>2023-04-05T02:28:29Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=78b6369e6761c04d6aff2d115bafd8845e90e530'/>
<id>urn:sha1:78b6369e6761c04d6aff2d115bafd8845e90e530</id>
<content type='text'>
The HTML version of MyFirstContribution [1] does not render the
asterisks (*) meant to be typed in as glob patterns by the user, because
they are being interpreted as bold text delimiters.

[1]: Search for "pattern" in
https://git-scm.com/docs/MyFirstContribution#v2-git-send-email

Signed-off-by: Linus Arver &lt;linusa@google.com&gt;
Acked-by: Taylor Blau &lt;me@ttaylorr.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>e-mail workflow: Message-ID is spelled with ID in both capital letters</title>
<updated>2023-04-03T15:55:43Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2022-12-16T01:47:19Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=ba4324c4e1e32a28381ea1f4835b78e4c9d45575'/>
<id>urn:sha1:ba4324c4e1e32a28381ea1f4835b78e4c9d45575</id>
<content type='text'>
We used to write "Message-Id:" and "Message-ID:" pretty much
interchangeably, and the header name is defined to be case
insensitive by the RFCs, but the canonical form "Message-ID:" is
used throughout the RFC documents, so let's imitate it ourselves.

Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
Reviewed-by: Elijah Newren &lt;newren@gmail.com&gt;
</content>
</entry>
<entry>
<title>Documentation: fix typo</title>
<updated>2022-11-14T23:14:58Z</updated>
<author>
<name>Vlad-Stefan Harbuz</name>
<email>vlad@vladh.net</email>
</author>
<published>2022-11-13T12:48:09Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=c5353c455208452b8a0a0c675f39b6bd16a8f35c'/>
<id>urn:sha1:c5353c455208452b8a0a0c675f39b6bd16a8f35c</id>
<content type='text'>
Signed-off-by: Vlad-Stefan Harbuz &lt;vlad@vladh.net&gt;
Signed-off-by: Taylor Blau &lt;me@ttaylorr.com&gt;
</content>
</entry>
<entry>
<title>Documentation: clean up a few misspelled word typos</title>
<updated>2022-09-21T17:28:35Z</updated>
<author>
<name>Jacob Stopak</name>
<email>jacob@initialcommit.io</email>
</author>
<published>2022-09-20T02:45:56Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=72991ff558585490aa4284c0b8ca1f13e86f0f18'/>
<id>urn:sha1:72991ff558585490aa4284c0b8ca1f13e86f0f18</id>
<content type='text'>
Used GNU "aspell check &lt;filename&gt;" to review various documentation
files with the default aspell dictionary. Ignored false-positives
between american and british english.

Signed-off-by: Jacob Stopak &lt;jacob@initialcommit.io&gt;
Reviewed-by: Eric Sunshine &lt;sunshine@sunshineco.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>MyFirstContribution: drop PR description for GGG single-patch contributions</title>
<updated>2022-05-13T01:10:00Z</updated>
<author>
<name>Philippe Blain</name>
<email>levraiphilippeblain@gmail.com</email>
</author>
<published>2022-05-12T23:43:37Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=4ec50080621f1072a51351cb0f93d1af15a3c531'/>
<id>urn:sha1:4ec50080621f1072a51351cb0f93d1af15a3c531</id>
<content type='text'>
By default, GitHub prefills the PR description using the commit message
for single-commit PRs. This results in a duplicate commit message below
the three-dash line if the contributor does not empty out the PR
description before submitting, which adds noise for reviewers.

Add a note to that effect in MyFirstContribution.txt.

This partly addresses:
https://github.com/gitgitgadget/gitgitgadget/issues/340

Signed-off-by: Philippe Blain &lt;levraiphilippeblain@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>MyFirstContribution: reference "The cover letter" in GitGitGadget section</title>
<updated>2022-05-13T01:10:00Z</updated>
<author>
<name>Philippe Blain</name>
<email>levraiphilippeblain@gmail.com</email>
</author>
<published>2022-05-12T23:43:36Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=c2cd4b592f89c4d11570c815f80b1a45266e4939'/>
<id>urn:sha1:c2cd4b592f89c4d11570c815f80b1a45266e4939</id>
<content type='text'>
The "Sending Patches via GitGitGadget" section mentions that the PR
title and description will be used as the cover letter, but does not
explain what is a cover letter or what should be included in it.

Refer readers to the new "The cover letter" section added in a previous
commit.

Signed-off-by: Philippe Blain &lt;levraiphilippeblain@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>MyFirstContribution: reference "The cover letter" in "Preparing Email"</title>
<updated>2022-05-13T01:09:59Z</updated>
<author>
<name>Philippe Blain</name>
<email>levraiphilippeblain@gmail.com</email>
</author>
<published>2022-05-12T23:43:35Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=e97d474c7a7ba5c5ed0cfa56e100a9b22feb69ff'/>
<id>urn:sha1:e97d474c7a7ba5c5ed0cfa56e100a9b22feb69ff</id>
<content type='text'>
The previous commit added a standalone section on the purpose of the
cover letter, drawing inspiration from the existing content of the
"Preparing Email" section.

Adjust "Preparing Email" to reference "The cover letter", to avoid
content duplication.

Also, use the imperative mode for the cover letter subject, as is done
in "The cover letter".

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