public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: YunQiang Su <wzssyqa@gmail.com>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: YunQiang Su <yunqiang.su@cipunited.com>,
	binutils@sourceware.org, iant@google.com,  ccoutant@gmail.com
Subject: Re: [PATCH v3 1/2] Gold/MIPS: Improve MIPS support in configure.tgt
Date: Wed, 30 Aug 2023 06:49:56 +0800	[thread overview]
Message-ID: <CAKcpw6VyxeU-q57pOoTb79qxtMvuGr04SWL1V2dM=yP8F5R5OA@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2308250426050.49340@angie.orcam.me.uk>

Maciej W. Rozycki <macro@orcam.me.uk> 于2023年8月25日周五 11:31写道:
>
> On Fri, 25 Aug 2023, YunQiang Su wrote:
>
> > @Maciej W. Rozycki How about this patch?
>
>  This will have to be split as I previously outlined.  Also I won't have

Generally, we should split patches by code logic, instead of make it fragments.
For distrubutions, cherry-pick patches from master is needed usally.
Fragmental patches will make lots of trobule to them.

We should have a trade off, instead of be extrame.

> any time to review patches in the next few weeks as I am out of capacity
> right now.
>
>   Maciej



-- 
YunQiang Su

      reply	other threads:[~2023-08-29 22:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-20 17:14 YunQiang Su
2023-08-20 17:14 ` [PATCH v3 2/2] MIPS: Use 64-bit a ABI by default for `mipsisa64*-*-linux*' targets YunQiang Su
2023-08-25  2:57 ` [PATCH v3 1/2] Gold/MIPS: Improve MIPS support in configure.tgt YunQiang Su
2023-08-25  3:31   ` Maciej W. Rozycki
2023-08-29 22:49     ` YunQiang Su [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='CAKcpw6VyxeU-q57pOoTb79qxtMvuGr04SWL1V2dM=yP8F5R5OA@mail.gmail.com' \
    --to=wzssyqa@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=ccoutant@gmail.com \
    --cc=iant@google.com \
    --cc=macro@orcam.me.uk \
    --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).