From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: [PATCH v2 0/2] MyFirstContribution: discuss then reroll
Date: Tue, 20 Oct 2026 16:22:40 -0700 [thread overview]
Message-ID: <20261020232242.2217109-1-gitster@pobox.com> (raw)
In-Reply-To: <xmqqa4o94e0r.fsf@gitster.g>
So here is a rerolled version of
https://lore.kernel.org/git/xmqqa4o94e0r.fsf@gitster.g/
Two major differences are:
* The shuffling of the order of descriptions, so that we discuss
reviewing process before we talk about v2, is split out into a
separate patch and has become [1/2].
* Redundant caution against sending updates too quickly/often has
been consolidated into one description, mixed with the new text
I wrote for v1 and copyedited. This is now [2/2].
The diff with v1 and the end image of this series is not really
worth showing, as the delta is large enough.
1/2: MyFirstContribution: move "how to send v2" after discussing reviews
2/2: MyFirstContribution: clarify that "reviewing" is a discussion
Documentation/MyFirstContribution.adoc | 287 ++++++++++++-------------
1 file changed, 139 insertions(+), 148 deletions(-)
--
2.56.0-321-g29a826976d
next prev parent reply other threads:[~2026-10-20 23:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 20:43 [PATCH] MyFirstContribution: move preparation of v2 after review discussion Junio C Hamano
2026-10-20 14:33 ` Patrick Steinhardt
2026-10-20 16:32 ` Junio C Hamano
2026-10-20 23:22 ` Junio C Hamano [this message]
2026-10-20 23:22 ` [PATCH v2 1/2] MyFirstContribution: move "how to send v2" after discussing reviews Junio C Hamano
2026-10-21 8:49 ` Patrick Steinhardt
2026-10-20 23:22 ` [PATCH v2 2/2] MyFirstContribution: clarify that "reviewing" is a discussion Junio C Hamano
2026-10-21 8:49 ` Patrick Steinhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261020232242.2217109-1-gitster@pobox.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox