From: "Lev R. Oshvang ." <levonshe@gmail.com>
To: kernelnewbies@kernelnewbies.org
Subject: Why my patch in lore archive doe not have mbox?
Date: Fri, 8 May 2020 10:21:05 +0300 [thread overview]
Message-ID: <CAP22eLENtCJXhi=jO9M4N3zJEu0gz=-4V5J3Cq4-3f=ZY5gFDw@mail.gmail.com> (raw)
Some time ago I posted patch to linux-integrity
https://lore.kernel.org/linux-integrity/20200330122434.GB28214@kl/
2 questions:
1. Linux-integrity maintainer, Mimi Zohar, rule this patch out.
How can I arque with this ruling?
2. Why this patch does not have mbox.gz ?
Thanks,
Lev
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next reply other threads:[~2020-05-08 7:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 7:21 Lev R. Oshvang . [this message]
2020-05-08 7:32 ` Why my patch in lore archive doe not have mbox? Greg KH
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='CAP22eLENtCJXhi=jO9M4N3zJEu0gz=-4V5J3Cq4-3f=ZY5gFDw@mail.gmail.com' \
--to=levonshe@gmail.com \
--cc=kernelnewbies@kernelnewbies.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).