From: Jan Beulich <jbeulich@suse.com>
To: Matthieu Longo <matthieu.longo@arm.com>
Cc: Richard Earnshaw <richard.earnshaw@arm.com>,
Nick Clifton <nickc@redhat.com>,
binutils@sourceware.org
Subject: Re: [PATCH v1 1/3] gas: minor reformatting in command line help and doc
Date: Wed, 3 Jul 2024 09:44:53 +0200 [thread overview]
Message-ID: <d548e96d-0ae2-4743-b119-de415117a64c@suse.com> (raw)
In-Reply-To: <20240702174003.1424939-2-matthieu.longo@arm.com>
On 02.07.2024 19:40, Matthieu Longo wrote:
>
> - help message: add a comma between the short and long option
> - as doc:
> - brief summary of how to invoke gas: separate [-w] [-x] on a new line as those
> two options have nothing to do with the warning options.
> - reordering of the warning options to have the same order as the listing.
> - no-warn option description: change an "and" to a "or", as it is either the short
> or long option to use, but not both at the same time.
> - remove trailing whitespaces.
> ---
> gas/as.c | 8 ++++----
> gas/as.h | 2 +-
> gas/doc/as.texi | 27 +++++++++++++++------------
> 3 files changed, 20 insertions(+), 17 deletions(-)
Okay.
Jan
next prev parent reply other threads:[~2024-07-03 7:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 17:40 [PATCH v1 0/3] gas: add command line option to inhibit info messages Matthieu Longo
2024-07-02 17:40 ` [PATCH v1 1/3] gas: minor reformatting in command line help and doc Matthieu Longo
2024-07-03 7:44 ` Jan Beulich [this message]
2024-07-18 16:05 ` Matthieu Longo
2024-07-02 17:40 ` [PATCH v1 2/3] gas: add new command line options to control diagnostic information messages Matthieu Longo
2024-07-03 7:55 ` Jan Beulich
2024-07-03 16:52 ` Matthieu Longo
2024-07-02 17:40 ` [PATCH v1 3/3] aarch64: testsuite: remove macro expansion messages from expected error output Matthieu Longo
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=d548e96d-0ae2-4743-b119-de415117a64c@suse.com \
--to=jbeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=matthieu.longo@arm.com \
--cc=nickc@redhat.com \
--cc=richard.earnshaw@arm.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).