From: John Kacur <jkacur@redhat.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Kurt Kanzenbach <kurt@linutronix.de>,
Clark Williams <williams@redhat.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: rt-tests release tarball location
Date: Fri, 10 Jan 2025 11:46:01 -0500 (EST) [thread overview]
Message-ID: <bb91bdda-8a07-1c99-5448-706460fdf1ce@redhat.com> (raw)
In-Reply-To: <20250109080555.WpQmRgu0@linutronix.de>
On Thu, 9 Jan 2025, Sebastian Andrzej Siewior wrote:
> On 2025-01-08 13:21:19 [-0500], John Kacur wrote:
> > We've been doing this for 15+ years. Normally I would expect the package
> > creators to come-up with a work around and not expect the people offering
> > the packages to accomdate your packaging software.
>
> This does not mean it does not deserve to be fixed once people complain.
> Debian and Fedora download the source package and host it themself so
> they don't rely on upstream's copy of it. Other, such as buildroot or
> Gentoo or even yocto download it on every request.
>
> > How many kernels back to you need to keep? Could we come up with a
> > compromise where we keep the newest kernel, plus say the last 3 in the
> > rt-tests directory before they get moved to the older directory?
>
> What I am asking is to either please keep all rt-tests releases in
> https://www.kernel.org/pub/linux/utils/rt-tests/
>
> but this would also mean that the older folder becomes removed and this
> might upset more people.
> Then there is the alternative especially if you prefer to have only the
> latest release on top to please keep all releases in
> https://www.kernel.org/pub/linux/utils/rt-tests/older/
>
> even the current one. This does not sound annoying, does it? The latter
> is what I do with RT patches while I release them after people
This option seems the least disruptive from my point of view.
I am now keeping all versions including the current version in
/pub/linux/utils/rt-tests/older
Thanks
John
> complained so I have the latest release in
> https://www.kernel.org/pub/linux/kernel/projects/rt/$version/
> and
> https://www.kernel.org/pub/linux/kernel/projects/rt/$version/older/
>
> > John
>
> Sebastian
>
>
next prev parent reply other threads:[~2025-01-10 16:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-28 10:43 rt-tests release tarball location Thomas Petazzoni
2025-01-07 9:41 ` Kurt Kanzenbach
2025-01-07 14:14 ` Sebastian Andrzej Siewior
2025-01-08 18:21 ` John Kacur
2025-01-08 19:05 ` Crystal Wood
2025-01-09 8:05 ` Sebastian Andrzej Siewior
2025-01-09 10:13 ` Tomas Glozar
2025-01-09 10:49 ` Sebastian Andrzej Siewior
2025-01-09 12:04 ` Jörg Sommer
2025-01-10 16:46 ` John Kacur [this message]
2025-08-13 21:06 ` Thomas Petazzoni
2025-08-18 19:18 ` John Kacur
2025-08-18 19:24 ` Thomas Petazzoni
2025-01-08 18:17 ` John Kacur
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=bb91bdda-8a07-1c99-5448-706460fdf1ce@redhat.com \
--to=jkacur@redhat.com \
--cc=bigeasy@linutronix.de \
--cc=kurt@linutronix.de \
--cc=linux-rt-users@vger.kernel.org \
--cc=thomas.petazzoni@bootlin.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox