From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Bob Peterson <rpeterso@redhat.com>
Cc: Steven Whitehouse <swhiteho@redhat.com>, linux-next@vger.kernel.org
Subject: Re: linux-next: unsigned commits in the gfs2 tree
Date: Tue, 4 Apr 2017 01:54:41 +1000 [thread overview]
Message-ID: <20170404015441.6e1ada59@canb.auug.org.au> (raw)
In-Reply-To: <201585065.10432946.1491226464555.JavaMail.zimbra@redhat.com>
Hi Bob,
On Mon, 3 Apr 2017 09:34:24 -0400 (EDT) Bob Peterson <rpeterso@redhat.com> wrote:
>
> As per your suggestion, I added a comment to the merge commit:
> https://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git/commit/?h=for-next&id=df029f7bc32dd76ca85ecddc90e7e6a051192f2d
>
> Let me know if you see a problem.
Looks good, thanks.
--
Cheers,
Stephen Rothwell
prev parent reply other threads:[~2017-04-03 15:54 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
2017-04-03 13:34 ` Bob Peterson
2017-04-03 15:54 ` Stephen Rothwell [this message]
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=20170404015441.6e1ada59@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-next@vger.kernel.org \
--cc=rpeterso@redhat.com \
--cc=swhiteho@redhat.com \
/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).