From: Tiezhu Yang <yangtiezhu@loongson.cn>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Question about when to push patches
Date: Sat, 7 Oct 2023 18:06:28 +0800 [thread overview]
Message-ID: <b6c47dc6-2b3d-f892-be6d-9b49d6c2ead4@loongson.cn> (raw)
Hi Tom,
I want to know what should I do for the patches only touch files related
with LoongArch in the future, self-approve or wait for "Approved-by" tag
from global maintainers?
Here are earlier discussions, but I am not sure it is suitable and valid
for now.
---
Thank you for the patch. This is ok, though as loongarch maintainer you
can self-approve patches that only touch this port's files.
> 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.
---
https://inbox.sourceware.org/gdb-patches/87h778kddl.fsf@tromey.com/
https://inbox.sourceware.org/gdb-patches/87v8vmdzvm.fsf@tromey.com/
Thanks,
Tiezhu
next reply other threads:[~2023-10-07 10:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-07 10:06 Tiezhu Yang [this message]
2023-10-07 23:22 ` Tom Tromey
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=b6c47dc6-2b3d-f892-be6d-9b49d6c2ead4@loongson.cn \
--to=yangtiezhu@loongson.cn \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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).