From: Kent Overstreet <kent.overstreet@gmail.com>
To: Jens Axboe <axboe@fb.com>
Cc: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] bcache revert
Date: Mon, 31 Aug 2015 11:29:14 -0800 [thread overview]
Message-ID: <20150831192914.GA1854@kmo-pixel> (raw)
In-Reply-To: <55E4A77F.7030802@fb.com>
On Mon, Aug 31, 2015 at 01:14:07PM -0600, Jens Axboe wrote:
> On 08/31/2015 01:00 PM, Kent Overstreet wrote:
> >Linus, please pull; this reverts a patch from Jens that was committed without
> >CCing be or being mailed out to any of the lists. Said patch wasn't in any way a
> >functional change and is something that damn well should have been discussed.
> >
> >Jens - what the goddamn fuck!? You've never touched the bcache code until now,
> >and when you finally get interested this is what you do!?
> >
> >While I am sympathetic to the arguments in favor of your patch, there _are_ some
> >damn good reasons I did it the way I did. If you want to have that discussion,
> >feel free to mail your patch out again after the revert.
>
> The patch was part of a larger series that I was working on, and I just
> wanted to flush out that dependency. Christoph review and acked it, it was
> by no means a sneaking in of a patch.
I didn't see it until I went to rebase bcachefs onto 4.2 this morning. I triple
checked; this patch is not in any mailing list archive. And you certainly didn't
try to contact me. How is that _not_ sneaking it in?
> So calm down. Is there a bug? The previous code was crap, having hidden
> returns in macros is horrible. The upstream bcache code has been effectively
> unmaintained for more than a year, and THIS patch is now a problem? Get
> real.
Oh, so you're taking over now? This is the first I've heard of it...
You may say the previous code was crap, but believe it or not I'm not an idiot
and I had real reasons for doing it that way. For damn sure if you want to start
changing stuff like this now it shouldn't be too much to ask that you _mail the
patch out_ so it can be discussed.
next prev parent reply other threads:[~2015-08-31 19:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-31 19:00 [GIT PULL] bcache revert Kent Overstreet
2015-08-31 19:14 ` Jens Axboe
2015-08-31 19:29 ` Kent Overstreet [this message]
2015-08-31 19:42 ` Jens Axboe
2015-08-31 19:53 ` Kent Overstreet
2015-08-31 20:06 ` Jens Axboe
2015-08-31 20:17 ` Kent Overstreet
2015-08-31 20:25 ` Jens Axboe
2015-08-31 20:42 ` Kent Overstreet
2015-08-31 20:47 ` Jens Axboe
2015-08-31 20:57 ` Kent Overstreet
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=20150831192914.GA1854@kmo-pixel \
--to=kent.overstreet@gmail.com \
--cc=axboe@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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