Workflows Archive on lore.kernel.org
 help / color / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	Thorsten Leemhuis <linux@leemhuis.info>,
	ksummit <ksummit-discuss@lists.linuxfoundation.org>,
	Greg KH <gregkh@linuxfoundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	workflows@vger.kernel.org
Subject: Re: [Ksummit-discuss] RFC: create mailing list "linux-issues" focussed on issues/bugs and regressions
Date: Tue, 23 Mar 2021 17:43:17 -0400
Message-ID: <20210323214317.t3igv3nan4lfolgr@chatter.i7.local> (raw)
In-Reply-To: <72f1c67bc8ad21bb1e5a7d77b88e2c3e50065e3b.camel@HansenPartnership.com>

On Tue, Mar 23, 2021 at 09:30:33AM -0700, James Bottomley wrote:
> > I think the bulk of user issues are going to be regressions. Although
> > you may be in a better position to know for sure, but at least for
> > me, wearing my "user" hat, the thing that gets me the most is
> > upgrading to a new kernel and suddenly something that use to work no
> > longer does. And that is the definition of a regression. My test
> > boxes still run old distros (one is running fedora 13). These are the
> > boxes that catch the most issues, and if they do, they are pretty
> > much guaranteed to be a regression.
> > 
> > I like the "linux-regressions" mailing list idea.
> 
> Can't we use the fancy features of public inbox to get the best of both
> worlds?  Have the bug list (or even a collection of lists) but make the
> linux-regressions one a virtual list keying off an imap flag which a
> group of people control.  That way anything that is flagged as a
> regression appears in that public inbox.  I assume the search can be
> quite wide so we could flag a regression on any list indexed by lore?

There's a number of ways we can accomplish this, sure.

However, this functionality is not in production yet, and I'm not sure which
upcoming public-inbox features we'll be implementing as a public
lore.kernel.org service, which ones we'll only offer to kernel.org account
holders, and which ones should really be running locally by developers
themselves.

So, I don't want to say either yes or no to this one for the fear of
over-promising. I guess this is why I'm not in sales. :)

-K

  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
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 [this message]
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:
  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=20210323214317.t3igv3nan4lfolgr@chatter.i7.local \
    --to=konstantin@linuxfoundation.org \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@leemhuis.info \
    --cc=rostedt@goodmis.org \
    --cc=workflows@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

Workflows Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/workflows/0 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/ https://lore.kernel.org/workflows \
		workflows@vger.kernel.org
	public-inbox-index workflows

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.workflows


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git