Question about when to push patches

Question about when to push patches

[Tiezhu Yang]

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

Re: Question about when to push patches

[Tom Tromey]

>>>>> 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