From: Jens Axboe <axboe@kernel.dk>
To: Philipp Reisner <philipp.reisner@linbit.com>
Cc: drbd-dev@lists.linbit.com, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] drbd-8.4.2 for the linux-3.8 merge window
Date: Fri, 09 Nov 2012 15:50:24 +0100 [thread overview]
Message-ID: <509D1830.8010103@kernel.dk> (raw)
In-Reply-To: <509D10A3.8040203@kernel.dk>
On 2012-11-09 15:18, Jens Axboe wrote:
> On 2012-11-09 14:33, Philipp Reisner wrote:
>> Jens, here it is without the sysfs stuff
>
> Thanks, pulled into for-3.8/drivers
I didn't say anything, but I've been fuming a bit the last few series of
merge windows. You need to stop these insanely massive pull requests.
I've been large since this is "just a driver", but it can't continue. We
should have reached stability a long time ago. Your pull requests
contain a shit load of items, are you guys paying per commit? Look at
these:
drbd: Request lookup code cleanup (1)
drbd: Request lookup code cleanup (2)
drbd: Request lookup code cleanup (3)
drbd: Request lookup code cleanup (4)
or
drbd: conn_send_cmd2(): Return 0 upon success and an error code otherwise
drbd: _conn_send_cmd(): Return 0 upon success and an error code otherwise
drbd: _drbd_send_cmd(): Return 0 upon success and an error code otherwise
drbd: conn_send_cmd(): Return 0 upon success and an error code otherwise
along with FIFTY or so more of these. WTF is this?
drbd: Converted helper functions for drbd_send() to tconn
drbd: Converted drbd_send() from mdev to tconn
drbd: Converted drbd_send_fp() from mdev to tconn
...
I don't think I need to go on. So from now on, to get items into the
kernel, what you will do is:
- Stop doing insane commits like the above. It just doesn't make sense.
- Send pull requests in a timely fashion. No more of this "lets collect
ALL the things" then send it off. Collect small bug fixes, send those
off. Develop some feature or make some changes, send that off. Etc.
The fact that your initial pull request had to MASK all these commits
should have rung big bells in your head. It's a clear sign of a huge
problem in your development model. If you can't clean this up, then
it's not going in.
--
Jens Axboe
next prev parent reply other threads:[~2012-11-09 14:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-09 11:36 [GIT PULL] drbd-8.4.2 for the linux-3.8 merge window Philipp Reisner
2012-11-09 11:40 ` Jens Axboe
2012-11-09 12:42 ` Philipp Reisner
2012-11-09 12:56 ` Jens Axboe
2012-11-09 13:33 ` Philipp Reisner
2012-11-09 14:18 ` Jens Axboe
2012-11-09 14:50 ` Jens Axboe [this message]
2012-11-09 15:19 ` Philipp Reisner
2012-11-09 19:49 ` Jens Axboe
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=509D1830.8010103@kernel.dk \
--to=axboe@kernel.dk \
--cc=drbd-dev@lists.linbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=philipp.reisner@linbit.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