From: Ulrich Hecht <uli@fpond.eu>
To: cip-dev@lists.cip-project.org, Pavel Machek <pavel@denx.de>
Subject: Re: [cip-dev] Request for reviews for 4.4-st42, 4.4-cip77
Date: Mon, 10 Jul 2023 18:47:00 +0200 (CEST) [thread overview]
Message-ID: <1604792087.2619298.1689007620064@webmail.strato.com> (raw)
In-Reply-To: <ZKsPiq6+/Zx1CLHr@duo.ucw.cz>
Thanks for the reviews!
> On 07/09/2023 9:50 PM CEST Pavel Machek <pavel@denx.de> wrote:
> a| 61256d2d6 None o+ | netfilter: nft_dynset: do not reject set updates with NFT_SET_EVAL
>
> Usual marking is "Commit xxx upstream.", this one has [ xxx ].
That's how the commits come in from stable. Are we using that in an automated way anywhere? If not, I'd rather not spend time fixing stuff like that.
CU
Uli
next prev parent reply other threads:[~2023-07-10 16:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 8:58 Request for reviews for 4.4-st42, 4.4-cip77 Ulrich Hecht
2023-07-09 19:50 ` Pavel Machek
2023-07-10 16:47 ` Ulrich Hecht [this message]
[not found] ` <17708F7C47443676.32062@lists.cip-project.org>
2023-08-01 15:24 ` Upstream hash format in commit messages; was: Re: [cip-dev] " Ulrich Hecht
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=1604792087.2619298.1689007620064@webmail.strato.com \
--to=uli@fpond.eu \
--cc=cip-dev@lists.cip-project.org \
--cc=pavel@denx.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