From: Mark Mitchell <mark@codesourcery.com>
To: Richard Sandiford <richard@codesourcery.com>
Cc: Nick Clifton <nickc@redhat.com>, binutils@sources.redhat.com
Subject: Re: PATCH: Support "@file"
Date: Fri, 07 Oct 2005 14:23:00 -0000 [thread overview]
Message-ID: <434684E0.3080703@codesourcery.com> (raw)
In-Reply-To: <87wtkplh4j.fsf@talisman.home>
[-- Attachment #1: Type: text/plain, Size: 521 bytes --]
Richard Sandiford wrote:
> Mark Mitchell <mark@codesourcery.com> writes:
>
>>option in either single or double quotes. Any character (including a
>>backslash) may be included by prefixing the character to be included
>>character with a backslash.
>
> ^^^^^^^^^
> stray "character"?
Thanks!
I took the libiberty of checking in the attached patch, which removes
the last occurrence "character", which had clearly escaped (from my
machine)...
--
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com
(916) 791-8304
[-- Attachment #2: at.patch --]
[-- Type: text/plain, Size: 1285 bytes --]
2005-10-07 Mark Mitchell <mark@codesourcery.com>
* at-file.texi: Fix typo.
Index: at-file.texi
===================================================================
RCS file: /cvs/src/src/libiberty/at-file.texi,v
retrieving revision 1.1
diff -c -5 -p -r1.1 at-file.texi
*** at-file.texi 4 Oct 2005 05:34:17 -0000 1.1
--- at-file.texi 7 Oct 2005 14:20:16 -0000
*************** literally, and not removed.
*** 9,16 ****
Options in @var{file} are separated by whitespace. A whitespace
character may be included in an option by surrounding the entire
option in either single or double quotes. Any character (including a
backslash) may be included by prefixing the character to be included
! character with a backslash. The @var{file} may itself contain
! additional @@@var{file} options; any such options will be processed
! recursively.
--- 9,15 ----
Options in @var{file} are separated by whitespace. A whitespace
character may be included in an option by surrounding the entire
option in either single or double quotes. Any character (including a
backslash) may be included by prefixing the character to be included
! with a backslash. The @var{file} may itself contain additional
! @@@var{file} options; any such options will be processed recursively.
prev parent reply other threads:[~2005-10-07 14:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-26 23:13 Mark Mitchell
2005-09-27 2:33 ` Ben Elliston
2005-09-27 6:51 ` DJ Delorie
2005-09-30 15:47 ` Nick Clifton
2005-09-30 18:04 ` Mark Mitchell
2005-09-30 22:52 ` Mark Mitchell
2005-10-03 9:12 ` Nick Clifton
2005-10-03 19:40 ` Mark Mitchell
2005-10-04 6:52 ` Nick Clifton
2005-10-04 7:03 ` Mark Mitchell
2005-10-04 19:02 ` DJ Delorie
2005-10-06 11:45 ` Nick Clifton
2005-10-07 11:08 ` Richard Sandiford
2005-10-07 14:23 ` Mark Mitchell [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=434684E0.3080703@codesourcery.com \
--to=mark@codesourcery.com \
--cc=binutils@sources.redhat.com \
--cc=nickc@redhat.com \
--cc=richard@codesourcery.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).