All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Linus Arver via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Linus Arver <linusa@google.com>
Subject: Re: [PATCH v3 0/5] SubmittingPatches: clarify which branch to use
Date: Tue, 25 Jul 2023 22:15:09 -0700	[thread overview]
Message-ID: <xmqqpm4ffe3m.fsf@gitster.g> (raw)
In-Reply-To: <pull.1556.v3.git.1690340701.gitgitgadget@gmail.com> (Linus Arver via GitGitGadget's message of "Wed, 26 Jul 2023 03:04:56 +0000")

"Linus Arver via GitGitGadget" <gitgitgadget@gmail.com> writes:

> This series rewords the "base-branch" section (now renamed to
> "choose-starting-point") to be more informative in general to new
> contributors, who may not be as familiar with the various integration
> branches. Other smaller cleanups and improvements were made along the way.

Well, both of us forgot that the previous round has already been in
'next' for quite a while.

So, I've split the difference between the previous round and the
result of applying this round into two patches, and then added a bit
of fix-ups on top.  I'll send them out shortly.

Thanks.

  parent reply	other threads:[~2023-07-26  5:15 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-08  1:05 [PATCH 0/5] SubmittingPatches: clarify which branch to use Linus Arver via GitGitGadget
2023-07-08  1:05 ` [PATCH 1/5] SubmittingPatches: reword awkward phrasing Linus Arver via GitGitGadget
2023-07-08  5:37   ` Junio C Hamano
2023-07-08  1:05 ` [PATCH 2/5] SubmittingPatches: be more explicit Linus Arver via GitGitGadget
2023-07-08  5:36   ` Junio C Hamano
2023-07-13 21:03     ` Linus Arver
2023-07-13 21:10       ` Junio C Hamano
2023-07-08  1:05 ` [PATCH 3/5] SubmittingPatches: discuss subsystems separately from git.git Linus Arver via GitGitGadget
2023-07-08  1:05 ` [PATCH 4/5] SubmittingPatches: remove confusing guidance about base branches Linus Arver via GitGitGadget
2023-07-08  5:48   ` Junio C Hamano
2023-07-13 21:54     ` Linus Arver
2023-07-08  1:05 ` [PATCH 5/5] SubmittingPatches: define topic branches Linus Arver via GitGitGadget
2023-07-14  6:01 ` [PATCH v2 0/5] SubmittingPatches: clarify which branch to use Linus Arver via GitGitGadget
2023-07-14  6:01   ` [PATCH v2 1/5] SubmittingPatches: reword awkward phrasing Linus Arver via GitGitGadget
2023-07-14  6:01   ` [PATCH v2 2/5] SubmittingPatches: discuss subsystems separately from git.git Linus Arver via GitGitGadget
2023-07-14  6:01   ` [PATCH v2 3/5] SubmittingPatches: de-emphasize branches as starting points Linus Arver via GitGitGadget
2023-07-14  6:01   ` [PATCH v2 4/5] SubmittingPatches: emphasize need to communicate non-default " Linus Arver via GitGitGadget
2023-07-14  6:01   ` [PATCH v2 5/5] SubmittingPatches: simplify guidance for choosing a starting point Linus Arver via GitGitGadget
2023-07-14 17:31     ` Junio C Hamano
2023-07-26  1:36       ` Linus Arver
2023-07-26  2:31         ` Linus Arver
2023-07-26  4:41         ` Junio C Hamano
2023-07-26  3:04   ` [PATCH v3 0/5] SubmittingPatches: clarify which branch to use Linus Arver via GitGitGadget
2023-07-26  3:04     ` [PATCH v3 1/5] SubmittingPatches: reword awkward phrasing Linus Arver via GitGitGadget
2023-07-26  3:04     ` [PATCH v3 2/5] SubmittingPatches: discuss subsystems separately from git.git Linus Arver via GitGitGadget
2023-07-26  3:04     ` [PATCH v3 3/5] SubmittingPatches: de-emphasize branches as starting points Linus Arver via GitGitGadget
2023-07-26  3:05     ` [PATCH v3 4/5] SubmittingPatches: emphasize need to communicate non-default " Linus Arver via GitGitGadget
2023-07-26  3:05     ` [PATCH v3 5/5] SubmittingPatches: simplify guidance for choosing a starting point Linus Arver via GitGitGadget
2023-07-26  5:15     ` Junio C Hamano [this message]
2023-07-26 17:19       ` [PATCH v3 0/5] SubmittingPatches: clarify which branch to use Linus Arver
2023-07-26  5:16     ` [PATCH v3 6/5] SubmittingPatches: choice of base for fixing an older maintenance track Junio C Hamano
2023-07-26  5:40       ` Eric Sunshine
2023-07-26 16:36         ` Junio C Hamano
2023-07-26  5:17     ` [PATCH 7/5] SubmittingPatches: explain why 'next' and above are inappropriate base Junio C Hamano
2023-07-27 19:26       ` Linus Arver
2023-07-26  5:21     ` [PATCH 8/5] SubmittingPatches: use of older maintenance tracks is an exception Junio C Hamano
2023-07-27 19:35       ` Linus Arver
2023-07-27 20:08         ` Junio C Hamano

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=xmqqpm4ffe3m.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=linusa@google.com \
    /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.