On Monday, 20 May 2024 12:41:48 CEST Ben Hutchings wrote:
> > - Can I do anything for you?
>
> My top priority would be more computing resources for Salsa, and
> particularly for CI runners.
+1
That was the first thing that came to my mind too, but it felt out of place for
me to suggest that.
t the end of the day in local time.
[...]
> I have some specific questions to the Debian Kernel team.
>
> - Do you feel good when doing your work in Kernel team?
That depends very much on which work I'm doing. Some of it is quite
tedious (and I'm trying to automate some of that at
infrastructure.
I have some specific questions to the Debian Kernel team.
- Do you feel good when doing your work in Kernel team?
- Team metrics currently shows two current contributors
(Ben and Salvatore). Do you consider the workload well
shared in your team?
- Do you have some
Your message dated Thu, 24 Aug 2017 22:04:38 +0200
with message-id <20170824200438.r35vlqhwu236q6hq@eldamar.local>
and subject line Re: Bug#873046: linux-image-4.12.0-1-amd64:
changelog.Debian.gz should only have changes made by the Debian kernel team and
changelog.gz should have the up
nly changes/patches made
> by Debian for the distribution and all upstream changes made by
> kernel.org in its own changelog.gz . While I'm sure that the
> debian-kernel team would probably have done this with some reason that
> is somehow not apparent or unknown here.
>
> I did
changelog.gz . While I'm sure that the
debian-kernel team would probably have done this with some reason that
is somehow not apparent or unknown here.
I did look at
https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no=linux
to see if I could find any bug-report about changelogs but apparently
On Tue, 2010-07-06 at 18:02 +0530, Ritesh Raj Sarraf wrote:
Hello Debian Kernel Team,
I would like to participate in the Debian kernel efforts.
I have run through the (limited) information on the wiki but am not sure
where
to start.
From what I have understood, there's a loose team
Hello Debian Kernel Team,
I would like to participate in the Debian kernel efforts.
I have run through the (limited) information on the wiki but am not sure where
to start.
From what I have understood, there's a loose team based on architectures that
interest them. Are there teams also based
the stability != preempt seems no longer true as the preempt
path gets more testing out there.
I'm running my notebook with full preemption since years now, without
any problems. I had to use the -ck patches, though, as the normal
preemption did not work well enough for me. I didn't check how
to
stability concerns by the Debian Kernel Team.
Do these concerns still hold, now that more than 2 years have
passed?
well partialy
but due to shipment in all major distribution volountary preemption
is beeing reconsidered as well preempt_bkl
http://lists.debian.org/debian-kernel/2007/11/msg00496
# CONFIG_PREEMPT is not set
# CONFIG_PREEMPT_BKL is not set
By reading the bug log, I seem to understand that this is due to stability
concerns by the Debian Kernel Team.
Do these concerns still hold, now that more than 2 years have passed?
If I read /usr/share/doc/jackd/README.Debian correctly, activating
CONFIG_PREEMPT_NONE=y
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT is not set
# CONFIG_PREEMPT_BKL is not set
yep, this is current state.
By reading the bug log, I seem to understand that this is due to stability
concerns by the Debian Kernel Team.
Do these concerns still hold, now
by it.
The kernel team was supposed to be a place where we all took the
decision together, i remember when in helsinki, the debian kernel team
was an example of how well a team worked, a friendly place to be, where
has this gone ? Should this be how it ends ? Already many of the kernel
team joined the expulsion
13 matches
Mail list logo
