From: Matthias Andree <matthias.andree@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Aic7xxx 6.2.28 and Aic79xx 1.3.0 Released
Date: Sun, 26 Jan 2003 18:09:27 +0100 [thread overview]
Message-ID: <20030126170927.GA14059@merlin.emma.line.org> (raw)
In-Reply-To: <20030123.205853.127871890.davem@redhat.com>
On Thu, 23 Jan 2003, David S. Miller wrote:
> I'm glad that we've established that we both provide endless amounts
> of comedy for each other.
>
> Look Justin, the fact remains that you get paid top dollar to maintain
> the Linux Adaptec driver. If you can't be bothered to reliably
> integrate fixes that show up in Linus's and Marcelo's tree, then
> that's regretfully sad given your circumstances.
>
> Now that is what makes me laugh!
David,
this is not how distributed development can work. The communication
clearly is broken here.
Regardless of whether Linus' tree is broken or no, ALWAYS Cc: the fixes
-- even if trivial -- to the driver maintainer. It's as simple as that.
Same about complaints. If a tree breaks, complaining to the maintainer
in addition to Linus/Marcelo/Alan may yield a "Linus' merge is
incomplete, here's the missing bit" message from the maintainer.
It's all about communication. If maintainers drown in messages, they'll
tell this (Linus for example is notorious for dropping messages).
I don't mean to offend anyone, but what you expect looks like
clairvoyance to me, regardless of whether Justin gets paid or not, this
is simply not reasonable to expect.
Unless someone comes up with a "watchmydriver" script that checks the
ChangeSet figures of a set of files after every bk pull and complains if
Linus' tree complains unauthorized ChangeSets. I'm not sure if there is
an invariant tag that remains across getting bk patches applied or if
real diffs are needed. Larry or other BK experts might know more.
--
Matthias Andree
next prev parent reply other threads:[~2003-01-26 17:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-22 22:50 Justin T. Gibbs
2003-01-23 12:14 ` Denis Vlasenko
2003-01-23 15:08 ` Justin T. Gibbs
2003-01-23 23:42 ` Scott McDermott
2003-01-24 3:55 ` David S. Miller
2003-01-24 3:45 ` Justin T. Gibbs
2003-01-24 3:35 ` David S. Miller
2003-01-24 3:56 ` Justin T. Gibbs
2003-01-24 3:53 ` David S. Miller
2003-01-24 4:26 ` Justin T. Gibbs
2003-01-24 4:27 ` David S. Miller
2003-01-24 4:54 ` Justin T. Gibbs
2003-01-24 4:58 ` David S. Miller
2003-01-26 17:09 ` Matthias Andree [this message]
2003-01-26 18:13 ` Sam Ravnborg
2003-02-09 22:28 ` Aic7xxx 6.2.28, boot warnings David Fries
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=20030126170927.GA14059@merlin.emma.line.org \
--to=matthias.andree@gmx.de \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®