[lkml]   [2003]   [Jan]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Aic7xxx 6.2.28 and Aic79xx 1.3.0 Released
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!


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
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:32    [W:0.040 / U:0.296 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site