From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: Improvement suggestion for creation of next [Was: linux-next: manual merge of the dmaengine tree with the driver-core tree]
Date: Thu, 16 Sep 2021 11:52:29 +0200 [thread overview]
Message-ID: <20210916095229.cvsjr4wbro26gev7@pengutronix.de> (raw)
In-Reply-To: <20210916162740.3327df56@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 842 bytes --]
Hello Stephen,
On Thu, Sep 16, 2021 at 04:27:40PM +1000, Stephen Rothwell wrote:
> [Sorry this took so long]
No problem. Thanks for picking up my suggestion (and not loosing it in
your mailbox).
> I prefer to fetch all the trees (and run my checking scripts across
> them independently of the merge/build cycle. However, I have improved
> the merge commit messages (I think). Please check out today's
> linux-next.
Looks great. Thanks.
> I have decided to remove the SHA1 from the message, as you
> can see that from what is merged anyway.
I understand that starting from tomorrow the short log will be shorter
for the merge commits.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | https://www.pengutronix.de/ |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-09-16 9:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-23 5:53 linux-next: manual merge of the dmaengine tree with the driver-core tree Stephen Rothwell
2021-07-23 9:16 ` Uwe Kleine-König
2021-07-27 13:44 ` Vinod Koul
2021-07-27 18:02 ` Dave Jiang
2021-07-28 7:10 ` Improvement suggestion for creation of next [Was: linux-next: manual merge of the dmaengine tree with the driver-core tree] Uwe Kleine-König
2021-09-16 6:27 ` Stephen Rothwell
2021-09-16 9:52 ` Uwe Kleine-König [this message]
2021-09-16 12:23 ` Stephen Rothwell
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=20210916095229.cvsjr4wbro26gev7@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--subject='Re: Improvement suggestion for creation of next [Was: linux-next: manual merge of the dmaengine tree with the driver-core tree]' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).