From: "J. Bruce Fields" <bfields@fieldses•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: linux-next: bad commit in the nfsd tree
Date: Wed, 19 Nov 2014 15:50:56 -0500 [thread overview]
Message-ID: <20141119205056.GB14207@fieldses.org> (raw)
In-Reply-To: <20141119080411.09f6a811@canb.auug.org.au>
On Wed, Nov 19, 2014 at 08:04:11AM +1100, Stephen Rothwell wrote:
> Hi,
>
> I just noticed that the top commit of the nfsd tree (be603bbb7bc1
> "OOPS") has no Signed-off-by tags (or a real commit message at all) ...
Yes, sorry, I needed it as a temporary fix for a client-side bug (since
gone upstream) for my testing, but didn't mean for it to leak out.
Should be gone now.
--b.
prev parent reply other threads:[~2014-11-19 20:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 21:04 linux-next: bad commit in the nfsd tree Stephen Rothwell
2014-11-19 20:50 ` J. Bruce Fields [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=20141119205056.GB14207@fieldses.org \
--to=bfields@fieldses$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/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