public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: Tom Tromey <tom@tromey.com>,  gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: LoongArch: prepend tramp frame unwinder for signal
Date: Wed, 06 Apr 2022 08:56:29 -0600	[thread overview]
Message-ID: <87v8vmdzvm.fsf@tromey.com> (raw)
In-Reply-To: <09ec51e6-d931-8762-49e4-3ec450dea76c@loongson.cn> (Tiezhu Yang's message of "Wed, 6 Apr 2022 11:18:22 +0800")

> If I am understanding you correctly, what you said means that
> if the patches only touch files related with LoongArch, I can
> push them to the master first, and then send the patches with
> "COMMITTED" in the subject line to gdb-patches@sourceware.org,
> right?

Yes.  Normally I send the email first, then push.  But it really doesn't
matter hugely since email is asynchronous.

thanks,
Tom

      reply	other threads:[~2022-04-06 14:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-31 12:01 Tiezhu Yang
2022-04-04 16:43 ` Tom Tromey
2022-04-06  3:18   ` Tiezhu Yang
2022-04-06 14:56     ` Tom Tromey [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=87v8vmdzvm.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.org \
    --cc=yangtiezhu@loongson.cn \
    /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).