From: Hans Ulrich Niedermann <linux-kernel@n-dimensional.de>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Fixing 2.6.0's broken documentation references
Date: Thu, 08 Jan 2004 19:36:31 +0100 [thread overview]
Message-ID: <86vfnm5lu8.fsf@n-dimensional.de> (raw)
In-Reply-To: <20031227160834.2de6401d.akpm@osdl.org> (Andrew Morton's message of "Sat, 27 Dec 2003 16:08:34 -0800")
Andrew Morton <akpm@osdl.org> writes:
> Hans Ulrich Niedermann <linux-kernel@n-dimensional.de> wrote:
>> 1. How to consistently reference to doc files?
>> c) "Documentation/"
> Yes, c).
OK, I did that. Patches against 2.6.1-rc3 in separate mails.
I split the changes into two patches:
1. The Documentation/ part.
- Only changes documentation files.
- No conflicts with code patches possible.
2. The code comment part.
- Changes *.c, *.h, Kconfig and relates files.
- May cause conflicts with code patches.
Regards,
Uli
prev parent reply other threads:[~2004-01-08 18:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-27 13:12 Fixing 2.6.0's broken documentation references Hans Ulrich Niedermann
2003-12-28 0:08 ` Andrew Morton
2003-12-28 3:34 ` Thomas Molina
2003-12-28 10:48 ` Michael Still
2003-12-28 22:02 ` Randy.Dunlap
2004-01-08 18:36 ` Hans Ulrich Niedermann [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=86vfnm5lu8.fsf@n-dimensional.de \
--to=linux-kernel@n-dimensional.de \
--cc=akpm@osdl.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 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.