From: Bob Wilson <bwilson@tensilica.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] wrap long lines in doc
Date: Mon, 26 Mar 2007 21:26:00 -0000 [thread overview]
Message-ID: <46083A70.9030407@tensilica.com> (raw)
In-Reply-To: <uejnbafn6.fsf@gnu.org>
Eli Zaretskii wrote:
> I'm saying that it isn't worth the hassle to do such reformatting:
> makeinfo and TeX do that for you when they produce output. The
> Texinfo sources are not required to be especially beautiful.
Sure, but C code doesn't need to be beautiful either and yet we have a
convention about keeping the lines less than 80 columns. I find wrapped lines
hard to read, so I like to fix them.
Thanks for approving the change.
prev parent reply other threads:[~2007-03-26 21:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-26 17:20 Bob Wilson
2007-03-26 20:17 ` Eli Zaretskii
2007-03-26 20:29 ` Bob Wilson
2007-03-26 20:55 ` Eli Zaretskii
2007-03-26 21:26 ` Bob Wilson [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=46083A70.9030407@tensilica.com \
--to=bwilson@tensilica.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
/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