1 |
Am Freitag, 3. Januar 2020, 00:25:06 CET schrieb Mike Pagano: |
2 |
> On Thursday, January 2, 2020 3:32:12 PM EST Rolf Eike Beer wrote: |
3 |
> > > - Allowed a simple "Add keyword(s) <y..> for package <x>" interface, |
4 |
> > > |
5 |
> > > that intelligently created an issue and a target list, and then once |
6 |
> > > the list was built, constantly ensured the list to be valid, or |
7 |
> > > determined automatically when sub-work was completed and reducing the |
8 |
> > > published list automatically, and then responded to potential issues |
9 |
> > > based on changes in git, ( as opposed to being only triggered when |
10 |
> > > the bug was touched ) |
11 |
> > |
12 |
> > As someone who does both keywordings and stabilizations regularly on hppa |
13 |
> |
14 |
> > and sparc I think I must share a bit of my experiences: |
15 |
> <snip> |
16 |
> |
17 |
> hppa is making us keep old kernels around [1]. Should the kernel team be |
18 |
> doing more to get your attention then CC'ing hppa on all of the kernel |
19 |
> STABLEREQ bugs [2]? |
20 |
|
21 |
I only run vanilla-sources since there are still lot of cache corruption |
22 |
problems in hppa kernels, or whatever makes them flaky. |
23 |
|
24 |
Linux pioneer 5.4.6-parisc64 #1 SMP Fri Dec 27 10:23:09 CET 2019 parisc64 |
25 |
PA8800 (Mako) 9000/785/C8000 GNU/Linux |
26 |
Linux voyager 5.4.6-parisc #1 Fri Dec 27 15:46:43 CET 2019 parisc PA8600 (PCX- |
27 |
W+) 9000/785/C3600 GNU/Linux |
28 |
|
29 |
So _I_ personally would say just drop old kernels, but that is in no way |
30 |
authorative. |
31 |
|
32 |
Eike |