From: Eric Wong <email@example.com> To: firstname.lastname@example.org Cc: James Bottomley <James.Bottomley@hansenpartnership.com>, Steven Rostedt <email@example.com>, Thorsten Leemhuis <firstname.lastname@example.org>, email@example.com, Greg KH <firstname.lastname@example.org>, email@example.com Subject: Re: [Ksummit-discuss] RFC: create mailing list "linux-issues" focussed on issues/bugs and regressions Date: Tue, 23 Mar 2021 23:11:06 +0000 Message-ID: <20210323231106.GA7165@dcvr> (raw) In-Reply-To: <firstname.lastname@example.org> Konstantin Ryabitsev <email@example.com> wrote: > 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? The lei (local email interface) data model will have "labels"(*) and developers will be able to publish mail with it via static HTML/Atom/JSON feed via cronjob and whatnot. > 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, lei could offer read-write JMAP support; either as a CGI tied to Unix user accounts or some virtual user system. Some fixes I'm currently making to speed up the test suite will also make it more suitable for a largish virtual user system. > and which ones should really be running locally by developers > themselves. lei will be MY dream mail/git tool that fills in the gaps left by other tools; I hope it can make others happy, too :) > 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. :) Heh, same here. Once I start using lei to handle all of my mail and there's a data-loss bug, I could conceivably never know about it because the bug reports would be lost... :x  "labels" are "mailboxes" in JMAP-speak; and lei's per-user data model will be tied to JMAP. "keywords" are Maildir/IMAP-system flags (seen/flagged/answered/...). JMAP doesn't allow arbitrary keywords, but does allow arbitrary labels.
next prev parent 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 2021-03-23 23:11 ` Eric Wong [this message] 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=20210323231106.GA7165@dcvr \ --firstname.lastname@example.org \ --cc=James.Bottomley@hansenpartnership.com \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.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 \ email@example.com 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