From: David Runge <dave@sleepmap.de>
To: linux-rt-users <linux-rt-users@vger.kernel.org>
Cc: Clark Williams <williams@redhat.com>
Subject: Re: Mixing upstreams
Date: Mon, 21 Nov 2022 21:11:45 +0100 [thread overview]
Message-ID: <Y3vbilrOjO4H5hXj@hmbx> (raw)
In-Reply-To: <Y3PFg2FlGMaVb2zd@hmbx>
[-- Attachment #1: Type: text/plain, Size: 1410 bytes --]
On 2022-11-15 17:59:36 (+0100), David Runge wrote:
> 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
To follow up on my own message above, I would like to mention that
mixing upstreams makes it much harder to properly track the releases of
the realtime kernels, as I can no longer rely on tags in those
repositories without ignore a list of arbitrary strings (which may grow
over time if someone with push access keeps pushing tags from the other
repository).
It would be really great to get a reply about this.
Best,
David
--
https://sleepmap.de
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2022-11-21 20:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 16:59 Mixing upstreams David Runge
2022-11-21 20:11 ` David Runge [this message]
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=Y3vbilrOjO4H5hXj@hmbx \
--to=dave@sleepmap.de \
--cc=linux-rt-users@vger.kernel.org \
--cc=williams@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.