From: Pavel Machek <pavel@denx.de>
To: uli@fpond.eu, cip-dev@lists.cip-project.org
Subject: 4.4 steps towards release
Date: Mon, 9 Jan 2023 16:53:25 +0100 [thread overview]
Message-ID: <Y7w4dfYgh7d10IdS@duo.ucw.cz> (raw)
[-- Attachment #1: Type: text/plain, Size: 690 bytes --]
Hi!
For 4.4 -st release, I'd suggest these steps:
- sign off the patches
- push that to linux-4.4.y-st-rc @ kernel.org
- update v4.4.org
For patches that were applied automatically, I don't think we need to
additional review. For the others, I guess you should send list to
cip-dev, and someone will take a look.
For updating 4.4-cip tree, just checkout linux-4.4.y-cip and merge
-st. Iwamatsu is doing 4.4-cip releases, so I was just asking him to
do them, he handles 4.4-cip-rebase.
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next reply other threads:[~2023-01-09 15:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 15:53 Pavel Machek [this message]
2023-01-10 8:14 ` [cip-dev] 4.4 steps towards release Ulrich Hecht
2023-01-15 22:09 ` Pavel Machek
2023-01-16 1:08 ` Ulrich Hecht
2023-01-17 20:50 ` Pavel Machek
2023-01-18 5:57 ` 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=Y7w4dfYgh7d10IdS@duo.ucw.cz \
--to=pavel@denx.de \
--cc=cip-dev@lists.cip-project.org \
--cc=uli@fpond.eu \
/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