From: Adrian Bunk <bunk@fs.tum.de>
To: linux-kernel@vger.kernel.org,
Hans Ulrich Niedermann <linux-kernel@n-dimensional.de>
Subject: Re: [2.6 patch] Canonically reference files in Documentation/ code comments part
Date: Sat, 24 Apr 2004 17:41:19 +0200 [thread overview]
Message-ID: <20040424154118.GC146@fs.tum.de> (raw)
In-Reply-To: <20040424095628.B25661@flint.arm.linux.org.uk>
On Sat, Apr 24, 2004 at 09:56:28AM +0100, Russell King wrote:
> On Sat, Apr 24, 2004 at 01:10:58AM +0200, Adrian Bunk wrote:
> > Below is an updated version of a patch by
> > Hans Ulrich Niedermann <linux-kernel@n-dimensional.de> to
> > change all references in comments to files in Documentation/ to start
> > with Documentation/ .
>
> I'd prefer to include the 'linux/' part so its obvious that we're
> referring to the kernel tree. I've given people pointers to files
> in the past, and just giving "Documentation/foo/bar" usually results
> in "I've looked on the web here, there and somewhere else and can't
> find the file."
Arguments in favor of this patch:
- it's more common in the kernel to start the reference at the top
of the kernel source
- the name of the directory os not linux but linux-<version>
But I don't have a that strong opinion on this issue.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2004-04-24 15:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-23 23:10 [2.6 patch] Canonically reference files in Documentation/ code comments part Adrian Bunk
2004-04-24 8:56 ` Russell King
2004-04-24 15:41 ` Adrian Bunk [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-04 23:07 Adrian Bunk
2004-07-06 21:36 Adrian Bunk
2004-07-07 2:20 ` John Lenz
2004-07-30 20:14 Adrian Bunk
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=20040424154118.GC146@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=linux-kernel@n-dimensional.de \
--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