From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Andreas Gruenbacher <agruenba@redhat.com>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-xfs@vger.kernel.org, Dave Chinner <david@fromorbit.com>,
LKML <linux-kernel@vger.kernel.org>,
Eric Sandeen <sandeen@sandeen.net>,
Christoph Hellwig <hch@lst.de>,
linux-ext4 <linux-ext4@vger.kernel.org>,
"Theodore Ts'o" <tytso@mit.edu>,
riteshh@linux.ibm.com, Goldwyn Rodrigues <rgoldwyn@suse.de>,
linux-btrfs@vger.kernel.org
Subject: Re: [GIT PULL] iomap: new code for 5.9-rc1
Date: Wed, 5 Aug 2020 09:31:26 -0700 [thread overview]
Message-ID: <20200805163126.GC6107@magnolia> (raw)
In-Reply-To: <20200805162349.GB6107@magnolia>
On Wed, Aug 05, 2020 at 09:23:49AM -0700, Darrick J. Wong wrote:
> On Wed, Aug 05, 2020 at 05:54:31PM +0200, Andreas Gruenbacher wrote:
> > Hi Darrick,
> >
> > On Wed, Aug 5, 2020 at 5:40 PM Darrick J. Wong <djwong@kernel.org> wrote:
> > > ----------------------------------------------------------------
> > > Andreas Gruenbacher (1):
> > > iomap: Make sure iomap_end is called after iomap_begin
> >
> > that commit (d1b4f507d71de) contains the following garbage in the
> > commit message:
> >
> > The message from this sender included one or more files
> > which could not be scanned for virus detection; do not
> > open these files unless you are certain of the sender's intent.
> >
> > ----------------------------------------------------------------------
> >
> > How did it come to that?
>
> I have no idea. It's not in the email that I turned into a patch, but
> golly roundtripping git patches through email and back to git sucks.
Aha-- the effing Oracle email virus scanner doesn't run on mails coming
in via mailing lists (which is the copy that I keep in my archive) but
the copy that you sent direct to me /did/ get a virus scan, which failed
because it's too stupid to recognize plain text, so the virus scanner
injected its stupid warning *into the message body*, and then I git-am'd
that without noticing.
S'ok, they're moving us to Exchange soon, so I expect never to hear from
any of you ever again.
--D
>
> Oh well, I guess I have to rebase the whole branch now.
>
> Linus: please ignore this pull request.
>
> --D
>
> >
> > Thanks,
> > Andreas
> >
>
prev parent reply other threads:[~2020-08-05 20:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-05 15:32 [GIT PULL] iomap: new code for 5.9-rc1 Darrick J. Wong
2020-08-05 15:54 ` Andreas Gruenbacher
2020-08-05 16:23 ` Darrick J. Wong
2020-08-05 16:31 ` Darrick J. Wong [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=20200805163126.GC6107@magnolia \
--to=darrick.wong@oracle.com \
--cc=agruenba@redhat.com \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=rgoldwyn@suse.de \
--cc=riteshh@linux.ibm.com \
--cc=sandeen@sandeen.net \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/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).