From: Nick Clifton <nickc@redhat.com>
To: mark@codesourcery.com
Cc: binutils@sources.redhat.com
Subject: Re: PATCH: Support "@file"
Date: Fri, 30 Sep 2005 15:47:00 -0000 [thread overview]
Message-ID: <433D556D.7080009@redhat.com> (raw)
In-Reply-To: <200509262117.j8QLHGxG022375@sethra.codesourcery.com>
Hi Mark,
> Here's a (boring) patch that makes binutils programs support "@file"
> arguments by using the new expandargv function in libiberty. Is this
> OK to apply?
Yes, please do.
> Where should documentation for the "@file" argument go?
In the linker doc file (ld/ld.texinfo), the binutils doc file
(binutils/doc/binutils.texi) *and* the --help output of these programs.
(Submitting a separate patch to do this is acceptable).
Question: is there any reason why you did not update GAS to use this
feature as well ? What about gprof too ?
> Should I add
> it to the list of options for every program in the binutils manual?
> Or, add a section up front with common options, of which this will be
> the only one? Or...?
Your choice. If you create a "common options" section you could also
put --version and --help in there, and maybe --verbose. (Not sure if
all commands accept it).
Cheers
Nick
next prev parent reply other threads:[~2005-09-30 15:05 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 [this message]
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
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=433D556D.7080009@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=mark@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).