From: David Runge <dave@sleepmap.de>
To: linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Mixing upstreams
Date: Tue, 15 Nov 2022 17:59:36 +0100 [thread overview]
Message-ID: <Y3PFg2FlGMaVb2zd@hmbx> (raw)
[-- Attachment #1: Type: text/plain, Size: 887 bytes --]
Hi!
I package the latest stable and the development version of linux-rt for
Arch Linux.
For this I follow the tags created in linux-stable-rt [1] and
linux-rt-devel [2] to rebase commits relevant for the distribution on
top of non-prerelease tags in those repositories.
Yesterday I noticed, that tags from linux-rt-devel (e.g. v6.0.5-rt14
[3]) started showing up in the linux-stable-rt repository.
Was this an oversight on your end or are you starting to migrate all
work on the patchset into one repository (which would also be easier for
me to mirror and track downstream)?
Best,
David
[1] https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git
[2] https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-rt-devel.git
[3] https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git/tag/?h=v6.0.5-rt14
--
https://sleepmap.de
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next reply other threads:[~2022-11-15 17:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 16:59 David Runge [this message]
2022-11-21 20:11 ` Mixing upstreams David Runge
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=Y3PFg2FlGMaVb2zd@hmbx \
--to=dave@sleepmap.de \
--cc=linux-rt-users@vger.kernel.org \
/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