Workflows Archive on
 help / color / Atom feed
From: Thorsten Leemhuis <>
To: Theodore Ts'o <>
Cc: Linus Torvalds <>,
	Konstantin Ryabitsev <>,
	Greg KH <>,,
	Linux Kernel Mailing List <>,
	ksummit <>,
	Sasha Levin <>
Subject: Re: [Ksummit-discuss] RFC: create mailing list "linux-issues" focussed on issues/bugs and regressions
Date: Tue, 23 Mar 2021 19:51:05 +0100
Message-ID: <> (raw)
In-Reply-To: <>

On 23.03.21 19:11, Theodore Ts'o wrote:
> On Tue, Mar 23, 2021 at 09:57:57AM +0100, Thorsten Leemhuis wrote:
>> On 22.03.21 22:56, Theodore Ts'o wrote:
>>> On Mon, Mar 22, 2021 at 08:25:15PM +0100, Thorsten Leemhuis wrote:
>>>> I agree to the last point and yeah, maybe regressions are the more
>>>> important problem we should work on – at least from the perspective of
>>>> kernel development.  But from the users perspective (and
>>>> reporting-issues.rst is written for that perspective) it feel a bit
>>>> unsatisfying to not have a solution to query for existing report,
>>>> regressions or not. Hmmmm...
>>> First of all, thanks for working on reporting-issues.rst.
>> Thx, very glad to hear that. I didn't get much feedback on it, which
>> made me wonder if anybody besides docs folks actually looked at it...
> I'll admit that I had missed your initial submission,

No wonder with all the lists and mails. :-D That's actually why I wanted
to point to the text on ksummit-list once in the near future after two
remaining issues with the text were solved (see below), but before
removing the "WIP" box at the top and deleting reporting-bugs.rst.

> but having
> looked at it, while I could imagine some nits where it could be
> improved,

Yeah, for sure, with such a text that will always be the case. And I
really would like if a few more people take a closer look and provide
feedback, that really helps to get such a text in shape. I have stared
so much at the text in recent months, that makes it quite easy to miss
typos and errors in the logical flow that a fresh pair of eyes will
immediately spot...

> in my opinion, it's strictly better than the older
> reporting-bugs doc.

Great, thx.

>> Hmmm, yeah, I like that idea. I'll keep it in mind for later: I would
>> prefer to get reporting-issues.rst officially blessed and
>> reporting-bugs.rst gone before working on further enhancements.
> Is there anyone following this thread who believes that there is
> anything we should change *before* oficially blessing
> reporting-issues.rst?  Given that Konstantin has already linked to
> reporting-issues from the front page of, I think
> we we should just go ahead and officially bless it and be done with
> it.   :-)

FWIW, here is my current todo list from the top of my head:

* get this patchset reviewed and applied:

* *afterwards* make sure Greg and/or Sasha (now CCed) check the text
from their point of view (above patchset changes quite a few things in
that area, that's why it needs to be applied first)

* get feedback reg. the two FIXME boxes remaining afterwards. One is
about bugzilla (```The old text took a totally different approach to```), the other about CCing LKML  (```Above
section tells users to always CC LKML […] Should we create mailing list
like```). But I guess the approach taken
should be fine for most people, so we could simply remove them. We can
still change things later anyway, I just put those boxes there to
highlight these differences to the old approach.

* remove the note at the top (```This document is being prepared to
replace 'Reporting bugs...``` and delete reporting-bugs.rst

> Once it is blessed, I'd also suggest putting a link to
> as an "other resources" at


Ciao, Thorsten

  reply index

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-22 15:18 Thorsten Leemhuis
2021-03-22 16:55 ` [Ksummit-discuss] " Lukas Bulwahn
2021-03-22 19:49   ` Thorsten Leemhuis
2021-03-22 17:16 ` Konstantin Ryabitsev
2021-03-22 17:57   ` [Ksummit-discuss] " James Bottomley
2021-03-22 18:34     ` Eric Wong
2021-03-22 18:55       ` Thorsten Leemhuis
2021-03-22 19:20         ` Konstantin Ryabitsev
2021-03-22 18:32 ` Linus Torvalds
2021-03-22 19:25   ` Thorsten Leemhuis
2021-03-22 21:56     ` [Ksummit-discuss] " Theodore Ts'o
2021-03-23  8:57       ` Thorsten Leemhuis
2021-03-23 15:01         ` Konstantin Ryabitsev
2021-03-23 19:09           ` Thorsten Leemhuis
2021-03-23 18:11         ` Theodore Ts'o
2021-03-23 18:51           ` Thorsten Leemhuis [this message]
2021-03-23 14:57     ` Luis Chamberlain
2021-03-23 16:20     ` Steven Rostedt
2021-03-23 16:30       ` [Ksummit-discuss] " James Bottomley
2021-03-23 21:43         ` Konstantin Ryabitsev
2021-03-23 23:11           ` Eric Wong
2021-03-23 18:07       ` Theodore Ts'o

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Workflows Archive on

Archives are clonable:
	git clone --mirror workflows/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 workflows workflows/ \
	public-inbox-index workflows

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone