From: Doug Ledford <dledford@redhat.com>
To: "Justin T. Gibbs" <gibbs@scsiguy.com>
Cc: Christoph Hellwig <hch@infradead.org>,
William Lee Irwin III <wli@holomorphy.com>,
Janet Morgan <janetmor@us.ibm.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] aic7xxx bouncing over 4G
Date: Sat, 21 Dec 2002 12:45:54 -0500 [thread overview]
Message-ID: <20021221174554.GA9703@redhat.com> (raw)
In-Reply-To: <4093022704.1040484612@aslan.scsiguy.com>
On Sat, Dec 21, 2002 at 08:30:12AM -0700, Justin T. Gibbs wrote:
> revision. I just do it as a single CSET with the comments dispersed
> into the individual files that the comments apply to.
Which is perfectly acceptable IMHO. There is no reason that a cset need
document all the details when the file logs already do. A cset need only
indicate what basic work is being done and maybe a list of files in the
cset. Doing a bk changes -v gets the file comments as well for those
people that want them.
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.
--
Doug Ledford <dledford@redhat.com> 919-754-3700 x44233
Red Hat, Inc.
1801 Varsity Dr.
Raleigh, NC 27606
next prev parent reply other threads:[~2002-12-21 17:45 UTC|newest]
Thread overview: 49+ 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 [this message]
2002-12-22 0:16 ` Linus Torvalds
2002-12-21 0:51 ` Samuel Flory
2002-12-28 5:32 ` Marcelo Tosatti
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: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 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:52 ` J.A. Magallon
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:19 ` Rik van Riel
2002-12-28 19:43 ` Tomas Szepe
[not found] ` <20021228231122.GC1999@werewolf.able.es>
2002-12-28 23:45 ` [BUG] new aic code [was Re: [PATCH] aic7xxx bouncing over 4G ] J.A. Magallon
2002-12-28 19:42 ` [PATCH] aic7xxx bouncing over 4G 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=20021221174554.GA9703@redhat.com \
--to=dledford@redhat.com \
--cc=gibbs@scsiguy.com \
--cc=hch@infradead.org \
--cc=janetmor@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=wli@holomorphy.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.