From: Tom Rini <trini@konsulko.com>
To: Heinrich Schuchardt <xypron.glpk@gmx.de>
Cc: Jerome Forissier <jerome.forissier@linaro.org>, u-boot@lists.denx.de
Subject: Re: [PATCH] doc/develop/sending_patches.rst: Clarify when to use which branch
Date: Sun, 15 Sep 2024 12:19:29 -0600 [thread overview]
Message-ID: <20240915181929.GA4252@bill-the-cat> (raw)
In-Reply-To: <4b1be536-86d8-4a43-9060-35e8c989e258@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 794 bytes --]
On Sun, Sep 15, 2024 at 07:00:08PM +0200, Heinrich Schuchardt wrote:
> On 8/26/24 18:39, Tom Rini wrote:
> > The previous wording on the paragraph about what branch to use when
> > submitting patches did not reflect how / when the next branch is
> > currently used. Reword this to note that master should be used for bug
> > and regression fixes, always, and that next should be used once it
> > opens, with -rc2.
> >
> > Reported-by: Jerome Forissier <jerome.forissier@linaro.org>
> > Signed-off-by: Tom Rini <trini@konsulko.com>
>
> Hello Tom,
>
> I missed that patch in my recent documentation pull-request.
>
> Maybe you just want to add it to master with whatever comes next.
>
> Reviewed-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
Will do, thanks.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2024-09-15 18:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-26 16:39 [PATCH] doc/develop/sending_patches.rst: Clarify when to use which branch Tom Rini
2024-08-26 16:46 ` Quentin Schulz
2024-08-26 17:01 ` [PATCH] doc/develop/sending_patches.rst: Reword where our git tree is slightly Tom Rini
2024-08-27 10:02 ` Quentin Schulz
2024-08-27 13:03 ` neil.armstrong
2024-08-26 17:27 ` [PATCH] doc/develop/sending_patches.rst: Clarify when to use which branch Jerome Forissier
2024-09-15 17:00 ` Heinrich Schuchardt
2024-09-15 18:19 ` Tom Rini [this message]
2024-09-15 18:23 ` Tom Rini
2024-09-15 18:25 ` Tom Rini
2024-09-16 20:41 ` (subset) " Tom Rini
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=20240915181929.GA4252@bill-the-cat \
--to=trini@konsulko.com \
--cc=jerome.forissier@linaro.org \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.de \
/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