From: Anuradha Ratnaweera <anuradha@gnu.org>
To: Andreas Bombe <andreas.bombe@munich.netsurf.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.5 and gcc v3 final
Date: Tue, 26 Jun 2001 21:04:12 +0600 [thread overview]
Message-ID: <20010626210412.B366@bee.lk> (raw)
In-Reply-To: <200106241733.f5OHXpW2000565@sleipnir.valparaiso.cl> <20010626004149.A3310@storm.local>
In-Reply-To: <20010626004149.A3310@storm.local>; from andreas.bombe@munich.netsurf.de on Tue, Jun 26, 2001 at 12:41:49AM +0200
On Tue, Jun 26, 2001 at 12:41:49AM +0200, Andreas Bombe wrote:
>
> But the first example contains three newlines, the second just one. A
> thing to keep in mind when going around fixing these multi line strings,
> explicit newlines have to be added.
Some code contains very long lines (around 150 characters per line) and others
tend to limit lines to 72-80 lines.
And strings have been broken in the middle _just_ to keep the lines short, and
sometimes without caring about the additional newline. In such cases, either,
the lines should be merged or a backslash should be added to the end(s) of the
line(s).
Please refer to my patch (GCC v3 warning fixes #1) for examples.
Anuradha
--
Debian GNU/Linux (kernel 2.4.6-pre5)
Journalism is literature in a hurry.
-- Matthew Arnold
prev parent reply other threads:[~2001-06-26 15:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-20 12:03 2.4.5 and gcc v3 final Kissandrakis S. George
2001-06-20 12:24 ` Anatoly Ivanov
2001-06-22 1:47 ` Fabian Arias
2001-06-22 6:29 ` Anatoly Ivanov
2001-06-24 3:52 ` Anuradha Ratnaweera
2001-06-24 16:33 ` Fabian Arias
2001-06-24 17:33 ` Horst von Brand
2001-06-25 16:58 ` Anuradha Ratnaweera
2001-06-25 18:59 ` [PATCH] GCC v3 warning fixes #1 (Was: Re: 2.4.5 and gcc v3 final) Anuradha Ratnaweera
2001-06-25 22:41 ` 2.4.5 and gcc v3 final Andreas Bombe
2001-06-26 15:04 ` Anuradha Ratnaweera [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=20010626210412.B366@bee.lk \
--to=anuradha@gnu.org \
--cc=andreas.bombe@munich.netsurf.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 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.