From: Tom Tromey <tom@tromey.com>
To: Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: Question about when to push patches
Date: Sat, 07 Oct 2023 17:22:09 -0600 [thread overview]
Message-ID: <871qe6xbku.fsf@tromey.com> (raw)
In-Reply-To: <b6c47dc6-2b3d-f892-be6d-9b49d6c2ead4@loongson.cn> (Tiezhu Yang's message of "Sat, 7 Oct 2023 18:06:28 +0800")
>>>>> Tiezhu Yang <yangtiezhu@loongson.cn> writes:
> 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?
If it only touches LoongArch-specific files, you can push them when you
want. An email is always required, that's all.
thanks,
Tom
prev parent reply other threads:[~2023-10-07 23:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-07 10:06 Tiezhu Yang
2023-10-07 23:22 ` 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=871qe6xbku.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).