From: Nicolas Schier <nsc@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Nathan Chancellor <nathan@kernel.org>,
linux-kbuild@vger.kernel.org
Subject: Updating Kbuild tree and contacts
Date: Thu, 18 Dec 2025 22:34:59 +0100 [thread overview]
Message-ID: <aURzg3BliUOYxnhI@levanger> (raw)
[-- Attachment #1: Type: text/plain, Size: 374 bytes --]
Hi Stephen,
Nathan and I have to reorganize the kbuild branches a bit. Can you
please update the branches for the kbuild tree
https://git.kernel.org/pub/scm/linux/kernel/git/kbuild/linux.git
(unchanged)
for linux-next to
kbuild-for-next and
kbuild-fixes-for-next
Please let me know if there are any issues or questions.
Thsnks and kind regards
Nicolas
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2025-12-18 21:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 21:34 Nicolas Schier [this message]
2025-12-19 9:44 ` Updating Kbuild tree and contacts Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2025-08-11 18:48 Nathan Chancellor
2025-08-11 22:34 ` 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=aURzg3BliUOYxnhI@levanger \
--to=nsc@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=sfr@canb.auug.org.au \
/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