From: Sam Ravnborg <sam@ravnborg.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Aic7xxx 6.2.28 and Aic79xx 1.3.0 Released
Date: Sun, 26 Jan 2003 19:13:01 +0100 [thread overview]
Message-ID: <20030126181301.GA1065@mars.ravnborg.org> (raw)
In-Reply-To: <20030126170927.GA14059@merlin.emma.line.org>
On Sun, Jan 26, 2003 at 06:09:27PM +0100, Matthias Andree wrote:
> 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.
That is not how things works out.
Doing trivial changes to 10+ Makefiles does not require to bother
10+ arch maintaners. Same goes for trivial fixes for any subsystem.
Linus pointed out what to do:
Keep a copy of the kernel used for last sync.
Take a copy of latest kernel.
Do a diff of all relevant files, and apply that before submitting.
When it was brought up last time, someone came with a small script to
do so.
No bk magic or other stuff needed, and I see that used by many arch
maintainers - otherwise they would loose to many trivial changes.
Sam
next prev parent reply other threads:[~2003-01-26 18:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-22 22:50 Aic7xxx 6.2.28 and Aic79xx 1.3.0 Released 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
2003-01-26 18:13 ` Sam Ravnborg [this message]
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=20030126181301.GA1065@mars.ravnborg.org \
--to=sam@ravnborg.org \
--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