From: Ben Hutchings <ben@decadent.org.uk>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Manoj Srivastava <manoj.srivastava.1962@gmail.com>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Liz Zhang <lizzha@microsoft.com>,
Lili Deng <v-lide@microsoft.com>,
Riku Voipio <riku.voipio@linaro.org>,
Michal Marek <michal.lkml@markovi.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kbuild: add workaround for Debian make-kpkg
Date: Sat, 09 Mar 2019 20:32:08 +0000 [thread overview]
Message-ID: <342abfaaff17af76aec43ae36ca09ebc43ea64ad.camel@decadent.org.uk> (raw)
In-Reply-To: <CAK7LNAQzfiZejYKKtFSineEwB5M_GcUktBmLgAGs2iC7i4Cbfw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 683 bytes --]
On Fri, 2019-03-08 at 15:42 +0900, Masahiro Yamada wrote:
> On Fri, Mar 8, 2019 at 6:56 AM Ben Hutchings <ben@decadent.org.uk> wrote:
[...]
> > I take it that you don't want kernel-package to be included in buster,
> > so can you open an RC bug to say so?
>
> Also, could you make sure it won't come back to bullseye or later ?
An RC (release-critical) bug will normally block a package from being
considered for any future release.
> How about Ubuntu? Is it out of your control?
Ubuntu's release management is independent of Debian's. I don't know
whether they consider RC bugs in Debian.
Ben.
--
Ben Hutchings
Knowledge is power. France is bacon.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-03-09 20:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 16:00 Masahiro Yamada
2019-03-06 20:59 ` Ben Hutchings
2019-03-06 21:01 ` Ben Hutchings
2019-03-07 4:03 ` Masahiro Yamada
2019-03-07 6:36 ` Ben Hutchings
[not found] ` <CABkpOEUqJWn62VZoTA5UEnbDieiYR9y3diRQhZuOVe6hOoBNhA@mail.gmail.com>
2019-03-07 21:56 ` Ben Hutchings
2019-03-08 6:42 ` Masahiro Yamada
2019-03-09 20:32 ` Ben Hutchings [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=342abfaaff17af76aec43ae36ca09ebc43ea64ad.camel@decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizzha@microsoft.com \
--cc=manoj.srivastava.1962@gmail.com \
--cc=michal.lkml@markovi.net \
--cc=riku.voipio@linaro.org \
--cc=v-lide@microsoft.com \
--cc=yamada.masahiro@socionext.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
all inboxes | Powered by JetHome®