From: Eli Zaretskii <eliz@gnu.org>
To: Bob Wilson <bwilson@tensilica.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] wrap long lines in doc
Date: Mon, 26 Mar 2007 20:55:00 -0000 [thread overview]
Message-ID: <uejnbafn6.fsf@gnu.org> (raw)
In-Reply-To: <46082D32.8030400@tensilica.com> (message from Bob Wilson on Mon, 26 Mar 2007 13:29:38 -0700)
> Date: Mon, 26 Mar 2007 13:29:38 -0700
> From: Bob Wilson <bwilson@tensilica.com>
> CC: gdb-patches@sources.redhat.com
>
> > Yes; but it's also unneeded.
>
> ? Are you saying that I should have just committed this without asking
> permission or that I should have left the long lines?
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.
Of course, once you did that, I'm only grateful to accept the changes.
Thanks!
> I don't work on GDB often so I'm just trying to be careful.
Thank you.
next prev parent reply other threads:[~2007-03-26 20:55 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 [this message]
2007-03-26 21:26 ` Bob Wilson
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=uejnbafn6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=bwilson@tensilica.com \
--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