From: YunQiang Su <wzssyqa@gmail.com>
To: Mark Wielaard <mark@klomp.org>
Cc: David Malcolm <dmalcolm@redhat.com>,
Patrick Palka <ppalka@redhat.com>,
gcc-patches <gcc-patches@gcc.gnu.org>,
buildbot@sourceware.org
Subject: Re: CI for "Option handling: add documentation URLs"
Date: Fri, 15 Mar 2024 15:33:28 +0800 [thread overview]
Message-ID: <CAKcpw6WqJdPZ51smLYpM2Fe1qrqNejXs1bszUcQtoMAQLpQw2g@mail.gmail.com> (raw)
In-Reply-To: <20240305202418.GA24213@gnu.wildebeest.org>
Great work. The CI works well now: it blames me ;)
https://builder.sourceware.org/buildbot/#/builders/269/builds/3846
When I add '-mstrict-align' option to MIPS,
the riscv.opt.urls, sysv4.opt.urls, xtensa.opt.urls are changed also.
(why they are effected?
So what's the best practice for this cases?
Should I push a new commit? Or in fact a single commit is preferred?
--
YunQiang Su
next prev parent reply other threads:[~2024-03-15 7:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231210233506.GC14917@gnu.wildebeest.org>
[not found] ` <20231214150143.3305661-1-dmalcolm@redhat.com>
2023-12-15 0:59 ` [PATCH 0/4] v3 of: Option handling: add documentation URLs Mark Wielaard
2023-12-15 14:47 ` David Malcolm
2024-01-04 14:57 ` CI for "Option handling: add documentation URLs" David Malcolm
2024-02-18 22:58 ` Mark Wielaard
2024-02-19 11:38 ` Mark Wielaard
2024-02-22 3:57 ` YunQiang Su
2024-02-24 17:42 ` Mark Wielaard
2024-03-03 20:04 ` Mark Wielaard
2024-03-04 13:48 ` David Malcolm
2024-03-05 12:06 ` Mark Wielaard
2024-03-05 13:34 ` David Malcolm
2024-03-05 20:24 ` Mark Wielaard
2024-03-15 7:33 ` YunQiang Su [this message]
2024-03-15 10:06 ` Mark Wielaard
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=CAKcpw6WqJdPZ51smLYpM2Fe1qrqNejXs1bszUcQtoMAQLpQw2g@mail.gmail.com \
--to=wzssyqa@gmail.com \
--cc=buildbot@sourceware.org \
--cc=dmalcolm@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mark@klomp.org \
--cc=ppalka@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).