From: Bob Peterson <rpeterso@redhat•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Steven Whitehouse <swhiteho@redhat•com>,
linux-next@vger•kernel.org,
Andreas Gruenbacher <agruenba@redhat•com>
Subject: Re: linux-next: unsigned commits in the gfs2 tree
Date: Sun, 26 Mar 2017 10:05:53 -0400 (EDT) [thread overview]
Message-ID: <1832386514.6929633.1490537153117.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20170327002220.0b800d75@canb.auug.org.au>
----- Original Message -----
| Hi all,
|
| I noticed that a few of the commits in the gfs2 tree
| (git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git#for-next)
| have no Signed-off-by from their committer.
|
| Also commit e8325475d61e ("Merge commit 'f9fe1c1' into for-next") seems
| to merge part of Dave Miller's net-next tree. You really should have
| an explanation of why this is being done.
| --
| Cheers,
| Stephen Rothwell
|
FYI--I fixed the commits in the gfs2 tree. Sorry about that.
Regards,
Bob Peterson
next prev parent reply other threads:[~2017-03-26 14:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-26 13:22 linux-next: unsigned commits in the gfs2 tree Stephen Rothwell
2017-03-26 13:56 ` Bob Peterson
2017-03-26 14:05 ` Bob Peterson [this message]
2017-04-03 13:34 ` Bob Peterson
2017-04-03 15:54 ` 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=1832386514.6929633.1490537153117.JavaMail.zimbra@redhat.com \
--to=rpeterso@redhat$(echo .)com \
--cc=agruenba@redhat$(echo .)com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=swhiteho@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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