public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
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:35:13 -0700	[thread overview]
Message-ID: <4C80C151.2050201@gmail.com> (raw)
In-Reply-To: <alpine.OSX.2.00.1009031906200.344@localhost>

On 09/03/2010 02:13 AM, Finn Thain wrote:
>
> On Fri, 3 Sep 2010, Justin P. Mattock wrote:
>
>> On 09/03/2010 01:47 AM, Finn Thain wrote:
>>>
>>> On Fri, 3 Sep 2010, Justin P. Mattock wrote:
>>>
>>>> On 09/03/2010 01:23 AM, Finn Thain wrote:
>>>>>
>>>>> URLs can't be split across lines usefully, so disregard the
>>>>> checkpatch complaint.
>>>>>
>>>>> Finn
>>>>>
>>>>
>>>> with the coding style, what files should ignore coding style with
>>>> the tab rule i.e. Kconfig *.c, *.h, README, etc... (from here
>>>> Kconfig make sense due to the ncurses interface..)
>>>
>>> I'm not sure what you mean (?)
>>>
>>> Kconfig seems to use the<...>  syntax for URLs. checkpatch doesn't
>>> complain about the ~90 character long URL in ./drivers/scsi/Kconfig...
>>>
>>> Finn
>>>
>>
>> yeah this is a bit confusing, especially with checkpatch in the mix.. So
>> if I understand correctly, using checkpatch, any address that uses the
>> column limit: (example)
>> + http://web.archive.org/web/*/http://www.unix-ag.org/Linux-Alpha/
>> + Architectures/Avanti.html.
>>
>> breaks checkpatch(without the<.....>) in any of the files? as for
>> Kconfig make the url long so the she looks pretty for the user..
>
> I don't know whether checkpatch special-cases Kconfig or angle brackets.
> You'd have to put it to the test. But it is not important.
>
> The point is, you can't line-wrap URLs without breaking software that
> looks for them (text editors, browsers, terminal emulators ... your own
> scripts too probably).
>
> Finn
>

so the safest is to just ignore the column limit for urls to make things 
legit.

Justin P. Mattock

  reply	other threads:[~2010-09-03  9:34 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 [this message]
2010-09-03  9:40                 ` Finn Thain
2010-09-03  9:58                   ` Justin P. Mattock
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=4C80C151.2050201@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