From: Dan Carpenter <dan.carpenter@oracle.com>
To: Fabio Aiuto <fabioaiuto83@gmail.com>
Cc: Greg KH <greg@kroah.com>, linux-staging@lists.linux.dev
Subject: Re: Bouncing messages from linux-staging@lists.linux.dev
Date: Fri, 7 May 2021 19:10:34 +0300 [thread overview]
Message-ID: <20210507161034.GH1955@kadam> (raw)
In-Reply-To: <20210507143201.GA1408@agape.jhs>
On Fri, May 07, 2021 at 04:32:02PM +0200, Fabio Aiuto wrote:
> On Fri, May 07, 2021 at 01:42:32PM +0200, Greg KH wrote:
> > On Fri, May 07, 2021 at 11:08:27AM +0200, Fabio Aiuto wrote:
> > > Hi all,
> > >
> > > On Fri, May 07, 2021 at 08:30:01AM +0000, linux-staging+owner@lists.linux.dev wrote:
> > > > Greetings!
> > > >
> > > > This is the mlmmj program managing the <linux-staging@lists.linux.dev>
> > > > mailing list.
> > > >
> > > > Some messages to you could not be delivered. If you're seeing this
> > > > message it means things are back to normal, and it's merely for your
> > > > information.
> > > >
> > > > Here is the list of the bounced messages:
> > > > - 2608
> > > >
> > > >
> > >
> > > what I'm supposed to do now if I'd want to retrieve the bounced message?
> >
> > What do you mean by "retrieve"?
>
> bring back home the message 2608 which is a message to me that could
> not be delivered. I mean, a message sent to me which was never delivered...
>
> If I didn't misunderstand.
Just ignore it. We all got the same message. If it's really important
people will resend.
regards,
dan carpenter
next prev parent reply other threads:[~2021-05-07 16:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1620376201-3408-mlmmj-4f932172@lists.linux.dev>
2021-05-07 9:08 ` Bouncing messages from linux-staging@lists.linux.dev Fabio Aiuto
2021-05-07 11:42 ` Greg KH
2021-05-07 14:32 ` Fabio Aiuto
2021-05-07 16:10 ` Dan Carpenter [this message]
2021-05-07 16:31 ` Fabio Aiuto
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=20210507161034.GH1955@kadam \
--to=dan.carpenter@oracle.com \
--cc=fabioaiuto83@gmail.com \
--cc=greg@kroah.com \
--cc=linux-staging@lists.linux.dev \
/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.