Thanks Ted, Casey and Al Viro. I am sorry for the inconvenience.
I tried to follow the instructions listed under
https://lore.kernel.org/lkml/[email protected]/
using git-send-email
Thought that will reply to the original thread with the original
subject . Let me know what I can do to correct this to avoid
confusion.
- Roy
On Thu, Apr 1, 2021 at 1:13 PM Theodore Ts'o <[email protected]> wrote:
>
> On Thu, Apr 01, 2021 at 07:48:30PM +0000, Al Viro wrote:
> > On Thu, Apr 01, 2021 at 12:17:44PM -0700, Roy Yang wrote:
> > > Both Android and Chrome OS really want this feature; For Container-Optimized OS, we have customers
> > > interested in the defense too.
> > >
> > > Thank you very much.
> > >
> > > Change-Id: I1eb1b726007aa8f9c374b934cc1c690fb4924aa3
> >
> > You forgot to tell what patch you are refering to. Your
> > Change-Id (whatever the hell that is) doesn't help at all. Don't
> > assume that keys in your internal database make sense for the
> > rest of the world, especially when they appear to contain a hash
> > of something...
>
> The Change-Id fails to have any direct search hits at lore.kernel.org.
> However, it turn up Roy's original patch, and clicking on the
> message-Id in the "In-Reply-Field", it apperas Roy was replying to
> this message:
>
> https://lore.kernel.org/lkml/[email protected]/
>
> which is the head of this patch series:
>
> Subject: [PATCH v8 0/6] Optionally randomize kernel stack offset each syscall
>
> That being said, it would have been better if the original subject
> line had been preserved, and it's yet another example of how the
> lore.kernel.org URL is infinitely better than the Change-Id. :-)
>
> - Ted
On Thu, Apr 01, 2021 at 01:49:17PM -0700, Roy Yang wrote:
> Thanks Ted, Casey and Al Viro. I am sorry for the inconvenience.
>
> I tried to follow the instructions listed under
> https://lore.kernel.org/lkml/[email protected]/
> using git-send-email
>
> Thought that will reply to the original thread with the original
> subject . Let me know what I can do to correct this to avoid
> confusion.
It did chain to the original thread; that's how I was able to figure
out the context. However, it looks like in your reply, you set the
subject to be:
[PATCH] Where we are for this patch?
And the problem is if someone had deleted the original e-mail chain
--- for example, optimizing the kernel stack is not one of the
subjects that I normally closely track, I had already deleted those
e-mail chains. So all I saw (and I suspect all Al saw) was a message
with the above subject line, and no context.
If you had kept the original subject line, then those of us who mostly
focus on file system stuff would have known that it's an area which is
covered by other maintainers, and we wouldn't have deleted your query
and let someone else respond.
Cheers,
- Ted
P.S. I personally find the use "git-send-email" to reply to be so
much of a pain that I just use a non-google.com address to which I can
use a traditional threaded mail-reader (such as mutt) and I can send
e-mail without having to worry about the DMARC nonsense. :-)