From: Andrew Morton <akpm@linux-foundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Junxiao Bi <junxiao.bi@oracle.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the mm tree
Date: Wed, 8 Jun 2022 19:22:05 -0700 [thread overview]
Message-ID: <20220608192205.66ebd59dae130d04fbd2b972@linux-foundation.org> (raw)
In-Reply-To: <20220609104456.009c53c6@canb.auug.org.au>
On Thu, 9 Jun 2022 10:44:56 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi all,
>
> Commit
>
> a4bf92bd6e08 ("ocfs2: kill EBUSY from dlmfs_evict_inode")
>
> is missing a Signed-off-by from its author.
>
> This is just a patch that went through a mailing list that rewrote its
> From address ... I wonder if we can make git use the Reply-To address
> for the author in these cases?
Thanks.
I fixed my copy.
Best to use an explicit From: line at top-of-changelog when using ocfs2-devel.
The ocfs2-devel list software is the worst thing since windows 95.
Does all sorts of weird stuff. Often patches which are cc:me simply
aren't on the list and weren't delivered to me. I have to hope like hell
that someone cc'ed a vger list.
next prev parent reply other threads:[~2022-06-09 2:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 0:44 linux-next: Signed-off-by missing for commit in the mm tree Stephen Rothwell
2022-06-09 2:22 ` Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-09-05 21:59 Stephen Rothwell
2022-11-23 22:13 Stephen Rothwell
2022-11-24 0:16 ` Andrew Morton
2022-12-17 20:59 Stephen Rothwell
2023-10-02 20:55 Stephen Rothwell
2023-10-02 22:06 ` Roman Gushchin
2023-11-20 21:39 Stephen Rothwell
2023-11-22 15:20 ` Fabio M. De Francesco
2024-08-18 22:03 Stephen Rothwell
2025-02-23 21:23 Stephen Rothwell
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=20220608192205.66ebd59dae130d04fbd2b972@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=junxiao.bi@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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