All of lore.kernel.org
 help / color / mirror / Atom feed
From: Akemi Yagi <toracat@elrepo.org>
To: stable@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 6.3.1
Date: Mon, 1 May 2023 22:28:13 -0000 (UTC)	[thread overview]
Message-ID: <u2pedt$k6q$1@ciao.gmane.io> (raw)
In-Reply-To: 2023050202-slouchy-princess-e7dd@gregkh

On Tue, 02 May 2023 06:40:03 +0900, Greg Kroah-Hartman wrote:

> On Mon, May 01, 2023 at 07:22:56AM +0100, Chris Clayton wrote:
>> 6.3.1 FTBFS thusly:
> 
> What is "FTBFS"?

"fails to build from source".

Akemi


WARNING: multiple messages have this Message-ID (diff)
From: Akemi Yagi <toracat@elrepo.org>
To: linux-kernel@vger.kernel.org
Cc: stable@vger.kernel.org
Subject: Re: Linux 6.3.1
Date: Mon, 1 May 2023 22:28:13 -0000 (UTC)	[thread overview]
Message-ID: <u2pedt$k6q$1@ciao.gmane.io> (raw)
In-Reply-To: 2023050202-slouchy-princess-e7dd@gregkh

On Tue, 02 May 2023 06:40:03 +0900, Greg Kroah-Hartman wrote:

> On Mon, May 01, 2023 at 07:22:56AM +0100, Chris Clayton wrote:
>> 6.3.1 FTBFS thusly:
> 
> What is "FTBFS"?

"fails to build from source".

Akemi


  reply	other threads:[~2023-05-01 22:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-30 23:55 Linux 6.3.1 Greg Kroah-Hartman
2023-04-30 23:55 ` Greg Kroah-Hartman
2023-05-01  6:22 ` Chris Clayton
2023-05-01  6:26   ` Chris Clayton
2023-05-01 21:40   ` Greg Kroah-Hartman
2023-05-01 22:28     ` Akemi Yagi [this message]
2023-05-01 22:28       ` Akemi Yagi
2023-05-01 23:43     ` Greg Kroah-Hartman
2023-05-02  5:07       ` Chris Clayton
2023-05-02  7:31       ` Greg Kroah-Hartman
2023-05-02 13:12         ` Chris Clayton
2023-05-06  0:52           ` Greg Kroah-Hartman
2023-05-06 10:03             ` Chris Clayton
  -- strict thread matches above, loose matches on Subject: below --
2023-05-01 13:03 Ronald Warsow
2023-04-30 23:41 Greg Kroah-Hartman
2023-04-30 23:41 ` Greg Kroah-Hartman

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='u2pedt$k6q$1@ciao.gmane.io' \
    --to=toracat@elrepo.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    /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.