linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Benjamin LaHaise <ben@communityfibre.ca>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: linux-mm@kvack.org - limping on a backup
Date: Mon, 28 Jun 2021 10:46:07 -0300	[thread overview]
Message-ID: <20210628134607.GA4604@ziepe.ca> (raw)
In-Reply-To: <20210625192607.GH4058@kvack.org>

On Fri, Jun 25, 2021 at 03:26:07PM -0400, Benjamin LaHaise wrote:
> On Fri, Jun 25, 2021 at 12:21:24PM -0700, James Bottomley wrote:
> > On Fri, 2021-06-25 at 13:12 -0400, Benjamin LaHaise wrote:
> > > On Fri, Jun 25, 2021 at 10:00:15AM -0700, James Bottomley wrote:
> > > > Perhaps it's time to move this list over to vger or the linux.dev
> > > > infrastructure now that it's being brought up?  We already migrated
> > > > the containers list without too much pain.
> > > 
> > > Maybe the btrfs bugs should get fixed.
> > 
> > I believe we can do both.
> 
> If I were unresponsive at fixing issues, I would understand the need to
> migrate services, 

Well, the DKIM issue has been left unresolved for a long time.

I saw on the bug conversation there seems to be no clear path to fix
it?

The LF/vger lists don't have this problem. The amount of email
impacted via recipient spam filtering seems to be increasing every
month, and tools like b4 don't work as intended.

It is not some minor complaint.

Jason


  parent reply	other threads:[~2021-06-28 13:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-22 14:59 linux-mm@kvack.org - limping on a backup Benjamin LaHaise
2021-06-24 12:12 ` David Sterba
2021-06-25 17:00 ` James Bottomley
2021-06-25 17:12   ` Benjamin LaHaise
2021-06-25 19:21     ` James Bottomley
2021-06-25 19:26       ` Benjamin LaHaise
2021-06-25 21:52         ` James Bottomley
2021-06-28 13:46         ` Jason Gunthorpe [this message]
2021-06-28 13:53           ` Benjamin LaHaise
2021-06-28 14:26             ` Jason Gunthorpe
2021-06-28 14:40               ` Benjamin LaHaise
2021-06-28 16:20                 ` Jason Gunthorpe

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=20210628134607.GA4604@ziepe.ca \
    --to=jgg@ziepe.ca \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=ben@communityfibre.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).