From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v4 0/2] MyFirstContribution: discuss then reroll
Date: Fri, 23 Oct 2026 07:33:13 -0700 [thread overview]
Message-ID: <xmqqcxt0bi6u.fsf@gitster.g> (raw)
In-Reply-To: <attTXu2sSy93_wyq@pks.im> (Patrick Steinhardt's message of "Fri, 23 Oct 2026 14:30:22 +0200")
Patrick Steinhardt <ps@pks.im> writes:
>> Relative to v3, this rewrites the "responding to reviews" section
>> more tightly, shaving about 1/5 words, without losing substance.
>
> Is this me or is there no v3? I cannot find it online, either.
Ah, v3 was never sent out, but it is v2 plus the "ah, did we lose
'state your plans' so how about incorporating it here?" we discussed
during v2 review.
prev parent reply other threads:[~2026-10-23 14:33 UTC|newest]
Thread overview: 15+ 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 ` [PATCH v2 0/2] MyFirstContribution: discuss then reroll Junio C Hamano
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
2026-10-21 16:22 ` Junio C Hamano
2026-10-22 11:24 ` Patrick Steinhardt
2026-10-22 21:14 ` [PATCH v4 0/2] MyFirstContribution: discuss then reroll Junio C Hamano
2026-10-22 21:14 ` [PATCH v4 1/2] MyFirstContribution: move "how to send v2" after discussing reviews Junio C Hamano
2026-10-22 21:14 ` [PATCH v4 2/2] MyFirstContribution: clarify that "reviewing" is a discussion Junio C Hamano
2026-10-23 12:30 ` [PATCH v4 0/2] MyFirstContribution: discuss then reroll Patrick Steinhardt
2026-10-23 14:33 ` Junio C Hamano [this message]
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=xmqqcxt0bi6u.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=ps@pks.im \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.