public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tim Bird <tim.bird@am.sony.com>
To: linux-kernel@vger.kernel.org
Cc: jw schultz <jw@pegasys.ws>
Subject: Re: [PATCH 2.6.2] Documentation/SubmittingPatches
Date: Fri, 06 Feb 2004 09:23:56 -0800	[thread overview]
Message-ID: <4023CDAC.3080807@am.sony.com> (raw)
In-Reply-To: <20040205201309.4dac8b8c.rddunlap@osdl.org>

> On Thu, 5 Feb 2004 19:45:09 -0800 jw schultz <jw@pegasys.ws> wrote:

> It would be _great_ if the Documentation was more accurate to the
 > taste of developers/maintainers...

> | > --- linux-2.6.2/Documentation/SubmittingPatches.orig    2004-02-04 22:57:55.818563016 -0800
> | > +++ linux-2.6.2/Documentation/SubmittingPatches 2004-02-04 23:01:28.799185040 -0800
> | > @@ -33,13 +33,15 @@

I thought the preferred method was:

--- linux-2.6.2.orig/Documentation/SubmittingPatches
+++ linux-2.6.2/Documentation/SubmittingPatches

In other words, I always thought you should have a whole parallel
original tree.  This more nicely captures multi-file changes, IMHO, and
I've seen this a great deal.

=============================
Tim Bird
Architecture Group Co-Chair
CE Linux Forum
Senior Staff Engineer
Sony Electronics
E-mail: Tim.Bird@am.sony.com
=============================


      reply	other threads:[~2004-02-06 17:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-05  7:23 [PATCH 2.6.2] Documentation/SubmittingPatches Bryan Whitehead
2004-02-05  8:18 ` Riley Williams
2004-02-05 19:05 ` Arthur Othieno
2004-02-06  3:45 ` jw schultz
2004-02-06  4:13   ` Randy.Dunlap
2004-02-06 17:23     ` Tim Bird [this message]

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=4023CDAC.3080807@am.sony.com \
    --to=tim.bird@am.sony.com \
    --cc=jw@pegasys.ws \
    --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