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 20:29:00 -0000 [thread overview]
Message-ID: <46082D32.8030400@tensilica.com> (raw)
In-Reply-To: <uhcs7ahes.fsf@gnu.org>
Eli Zaretskii wrote:
>> Date: Mon, 26 Mar 2007 10:20:21 -0700
>> From: Bob Wilson <bwilson@tensilica.com>
>>
>> Surely this must qualify as obvious
>
> 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 would have assumed the
former except that I promised to be cautious about invoking the "obvious" rule
after you objected to something I committed last fall (admittedly much less
obvious than this). I don't work on GDB often so I'm just trying to be careful.
> If all you did was type "M-q" in Emacs on each of these paragraphs,
> please go ahead and commit this.
Yes, that's all I did. I will commit it.
--Bob
next prev parent reply other threads:[~2007-03-26 20:29 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 [this message]
2007-03-26 20:55 ` Eli Zaretskii
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=46082D32.8030400@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