From: Michal Marek <mmarek@suse.cz>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Johann Felix Soden <johfel@gmx.de>, Jiri Kosina <jkosina@suse.cz>,
Randy Dunlap <rdunlap@xenotime.net>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix file references in Kconfig files
Date: Tue, 11 Oct 2011 14:41:36 +0200 [thread overview]
Message-ID: <4E943980.8040807@suse.cz> (raw)
In-Reply-To: <1318320079.18122.38.camel@x61.thuisdomein>
On 11.10.2011 10:01, Paul Bolle wrote:
> On Tue, 2011-10-11 at 01:10 +0200, Johann Felix Soden wrote:
>> This patch fixes file references to moved or deleted files
>> outside of Documentation/.
>
> Apparently you grepped on something like "<file:.*". This triggers an
> issue I've been wondering about a bit.
>
> Would anyone know why some file references are wrapped in a "<file:" -
> ">" pair while others are not? The same thing can be seen with "http://"
> links: some are wrapped in angle brackets while others are not. What do
> these brackets (and the "file:" prefix) actually provide?
I guess the plan was to display these references as clickable links in
the graphical front-ends, but this has never been implemented.
Michal
prev parent reply other threads:[~2011-10-11 12:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-03 23:11 [PATCH] Fix file references in the whole tree Johann Felix Soden
2011-10-04 23:09 ` Randy Dunlap
2011-10-10 18:37 ` [PATCH] ide: Fix file references in drivers/ide/ Randy Dunlap
2011-10-10 18:59 ` Paul Bolle
2011-10-10 19:17 ` David Miller
2011-10-10 18:58 ` [PATCH] Fix file references in the whole tree Randy Dunlap
2011-10-10 21:51 ` Jiri Kosina
2011-10-10 23:10 ` [PATCH] Fix file references in Kconfig files Johann Felix Soden
2011-10-11 8:01 ` Paul Bolle
2011-10-11 12:41 ` Michal Marek [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=4E943980.8040807@suse.cz \
--to=mmarek@suse.cz \
--cc=jkosina@suse.cz \
--cc=johfel@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--cc=rdunlap@xenotime.net \
--cc=torvalds@linux-foundation.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.