From: torvalds@transmeta.com (Linus Torvalds)
To: linux-scsi@vger.kernel.org
Subject: Re: [PATCH] aic7xxx bouncing over 4G
Date: Sun, 22 Dec 2002 00:16:22 +0000 (UTC) [thread overview]
Message-ID: <au308m$14b$1@penguin.transmeta.com> (raw)
In-Reply-To: 20021221174554.GA9703@redhat.com
In article <20021221174554.GA9703@redhat.com>,
Doug Ledford <dledford@redhat.com> wrote:
>
>I actually like the individual file comments part of the cset setup. It's
>what my preferred use is when I'm making my own patches. Make the cset
>have a summary of the major changes, then let each file have it's own
>detail change information.
I do that too, but on the whole I tend to think that if the per-file
comments are really needed (as opposed to being just nice extra and
mostly uninteresting details), there's something wrong with the CSet.
For example, all the regular changelog tools just use the main cset
comment, and discard the file comments. So my own rule is that the file
comments should be something fairly small and insignificant, and a good
cset should really be sufficiently explained by the cset comment.
If the changes are so involved that you only end up condensing the
per-file comments for the global cset comment, and the per-file comments
are really interesting, then maybe that cset should have been split up
in the first place..
Linus
next prev parent reply other threads:[~2002-12-22 0:18 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-21 0:12 [PATCH] aic7xxx bouncing over 4G Janet Morgan
2002-12-21 0:23 ` Justin T. Gibbs
2002-12-21 0:29 ` William Lee Irwin III
2002-12-21 0:59 ` Justin T. Gibbs
2002-12-21 1:35 ` William Lee Irwin III
2002-12-21 1:59 ` Justin T. Gibbs
2002-12-21 4:10 ` David S. Miller
2002-12-21 15:19 ` Justin T. Gibbs
2002-12-21 21:41 ` David S. Miller
2002-12-21 7:10 ` Erik Andersen
2002-12-21 15:23 ` Justin T. Gibbs
2002-12-21 8:55 ` Christoph Hellwig
2002-12-21 15:30 ` Justin T. Gibbs
2002-12-21 17:45 ` Doug Ledford
2002-12-22 0:16 ` Linus Torvalds [this message]
2002-12-21 0:51 ` Samuel Flory
2002-12-28 5:32 ` Marcelo Tosatti
2002-12-28 9:16 ` Tomas Szepe
2002-12-28 13:33 ` Rik van Riel
2002-12-28 13:40 ` Tomas Szepe
2002-12-28 16:23 ` Tony Spinillo
2002-12-28 15:00 ` James Bottomley
2002-12-28 19:16 ` Justin T. Gibbs
2002-12-28 20:16 ` James Bottomley
2002-12-28 21:02 ` Justin T. Gibbs
2002-12-28 20:18 ` Andrew Morton
2002-12-28 20:50 ` Justin T. Gibbs
2002-12-28 22:24 ` James Bottomley
2002-12-28 22:31 ` Justin T. Gibbs
2002-12-28 22:46 ` Andrew Morton
2002-12-28 19:13 ` Justin T. Gibbs
2002-12-28 19:19 ` Rik van Riel
2002-12-28 19:42 ` Doug Ledford
2002-12-28 21:04 ` Willy Tarreau
2002-12-28 22:37 ` David Lang
2002-12-29 12:54 ` Arjan van de Ven
2003-01-03 15:28 ` Justin T. Gibbs
2003-01-06 1:40 ` aic79xx bug? my stupidity? Roberto Peon
2003-01-06 1:46 ` Justin T. Gibbs
2002-12-30 21:06 ` [PATCH] aic7xxx bouncing over 4G Samuel Flory
2002-12-28 9:50 ` Christoph Hellwig
2002-12-30 1:23 ` Alan Cox
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='au308m$14b$1@penguin.transmeta.com' \
--to=torvalds@transmeta.com \
--cc=linux-scsi@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