From: "Maciej W. Rozycki" <macro@orcam.me.uk>
To: YunQiang Su <syq@debian.org>
Cc: YunQiang Su <yunqiang.su@cipunited.com>,
binutils@sourceware.org, xry111@xry111.site,
richard.sandiford@arm.com, jiaxun.yang@flygoat.com
Subject: Re: [PATCH] gas: documents .gnu_attribute Tag_GNU_MIPS_ABI_MSA
Date: Fri, 19 May 2023 13:41:09 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.2.21.2305191319480.50034@angie.orcam.me.uk> (raw)
In-Reply-To: <CAKcpw6XiPUqnKz4ntUG71-Oh7Nn4mUQ-2A1gqFac3u3534+SrA@mail.gmail.com>
On Fri, 19 May 2023, YunQiang Su wrote:
> > > It is added since 2016 by
> > > Add support for .MIPS.abiflags and .gnu.attributes sections
> > > b52717c0e104eb603e8189c3c0d3658ef5d903f5
> > > But never documented.
> >
> > Hmm, I can see this has been committed, but who has actually approved
> > this change?
> >
>
> Yes. I believe this change is an "obvious" change, as descripted in
>
> Read-write Git access - GNU Project: https://gcc.gnu.org/gitwrite.html
Under this rule you can push a commit right away as long as you post the
change committed to our mailing list afterwards, or if you post beforehand
mentioning that you intend to push unless you hear objections within some
reasonable time, but you do need to state there that the change has been
or will be committed under the "obviously correct" rule.
Also your change is actually not obviously correct, because it has a
defect in formatting: an overlong line that exceeds 79 columns (staying
within 74 is preferred where feasible).
Finally for a non-native English speaker it's always good to have
documentation changes reviewed as this is what our users will read, and
the last thing we want is documentation that seems unprofessional. In
this case you have an inconsistency between the two cases: one uses the
singular and the other one uses the plural form of the noun, which is bad
style. I find the style of the commit description so-so as well. Being
internal only it's less of a problem, albeit unfixable once pushed.
Maciej
next prev parent reply other threads:[~2023-05-19 12:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 9:27 YunQiang Su
2023-05-19 11:54 ` Maciej W. Rozycki
2023-05-19 12:16 ` YunQiang Su
2023-05-19 12:41 ` Maciej W. Rozycki [this message]
2023-06-15 3:50 ` Maciej W. Rozycki
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=alpine.DEB.2.21.2305191319480.50034@angie.orcam.me.uk \
--to=macro@orcam.me.uk \
--cc=binutils@sourceware.org \
--cc=jiaxun.yang@flygoat.com \
--cc=richard.sandiford@arm.com \
--cc=syq@debian.org \
--cc=xry111@xry111.site \
--cc=yunqiang.su@cipunited.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).