From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Finn Thain <fthain@telegraphics.com.au>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: Fwd: [PATCH 35/91] arch/m68k/q40/README Update broken web addresses in the arch directory.
Date: Fri, 03 Sep 2010 02:58:30 -0700 [thread overview]
Message-ID: <4C80C6C6.10506@gmail.com> (raw)
In-Reply-To: <alpine.OSX.2.00.1009031938070.344@localhost>
On 09/03/2010 02:40 AM, Finn Thain wrote:
>
>
> On Fri, 3 Sep 2010, Justin P. Mattock wrote:
>
>>
>> so the safest is to just ignore the column limit for urls to make things
>> legit.
>
> That's how I've dealt with URLs in C comments in the past, and no-one
> complained (and I don't see any decent alternative anyway).
>
> Finn
>
well, over here, I'm learning new things daily(so I thank you for your
patience), as for the url... makes sense...as for the mechanisms that
crap out with such changes... then maybe something as simple as /*...*/
for the compiler...(but who knows...main thing is making sure these urls
are working...), just checked most of the kernel, seems sane todo...just
a matter of patience and such...
Justin P. Mattock
next prev parent reply other threads:[~2010-09-03 9:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1283461746-7905-1-git-send-email-justinmattock@gmail.com>
[not found] ` <1283461746-7905-6-git-send-email-justinmattock@gmail.com>
2010-09-03 7:52 ` Fwd: [PATCH 36/91] arch/m68k/mac/macboing.c Update broken web addresses in the arch directory Geert Uytterhoeven
2010-09-03 8:14 ` Justin P. Mattock
2010-09-03 8:32 ` Finn Thain
2010-09-03 8:42 ` Geert Uytterhoeven
2010-09-03 10:42 ` Finn Thain
2010-09-04 4:59 ` Finn Thain
2010-09-03 8:20 ` Finn Thain
2010-09-03 8:31 ` Justin P. Mattock
[not found] ` <1283461746-7905-8-git-send-email-justinmattock@gmail.com>
2010-09-03 7:52 ` Fwd: [PATCH 38/91] arch/m68k/Kconfig " Geert Uytterhoeven
[not found] ` <1283461746-7905-7-git-send-email-justinmattock@gmail.com>
2010-09-03 7:53 ` Fwd: [PATCH 37/91] arch/m68k/mac/via.c " Geert Uytterhoeven
[not found] ` <1283461746-7905-5-git-send-email-justinmattock@gmail.com>
2010-09-03 7:54 ` Fwd: [PATCH 35/91] arch/m68k/q40/README " Geert Uytterhoeven
2010-09-03 8:23 ` Finn Thain
2010-09-03 8:35 ` Justin P. Mattock
2010-09-03 8:47 ` Finn Thain
2010-09-03 9:04 ` Justin P. Mattock
2010-09-03 9:13 ` Finn Thain
2010-09-03 9:35 ` Justin P. Mattock
2010-09-03 9:40 ` Finn Thain
2010-09-03 9:58 ` Justin P. Mattock [this message]
2010-09-03 8:57 ` Finn Thain
2010-09-03 9:12 ` Justin P. Mattock
2010-09-03 9:26 ` Finn Thain
2010-09-03 9:32 ` Justin P. Mattock
2010-09-03 9:40 ` Finn Thain
2010-09-03 10:00 ` Justin P. Mattock
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=4C80C6C6.10506@gmail.com \
--to=justinmattock@gmail.com \
--cc=fthain@telegraphics.com.au \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@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