public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Xi Ruoyao <xry111@xry111.site>
To: caiyinyu <caiyinyu@loongson.cn>,
	Noah Goldstein <goldstein.w.n@gmail.com>
Cc: "H.J. Lu" <hjl.tools@gmail.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH] x86: Fix bug about glibc.cpu.hwcaps.
Date: Thu, 09 Mar 2023 11:25:40 +0800	[thread overview]
Message-ID: <e47cd4b0b2053b7c0a850c9b7e89e66bf8e97970.camel@xry111.site> (raw)
In-Reply-To: <ce6fc262-f80e-a03d-4107-f629d234470c@loongson.cn>

On Thu, 2023-03-09 at 09:26 +0800, caiyinyu wrote:
> > It also doesn't have the BZ number in the commit message. In the future please
> > wait for approval before pushing.

My bad.  I thought the "OK" from H. J. was a formal approval and gave
some wrong advice.

> > 
> Ok. There are "Recorded in [BZ #30183]:" in the commit message and I 
> will append it on
> 
> the first line next time.
> 
> I mistakenly thought HJ is ok with

-- 
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University

  reply	other threads:[~2023-03-09  3:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-02  2:33 caiyinyu
2023-03-02  4:22 ` H.J. Lu
2023-03-07 12:45   ` caiyinyu
2023-03-07 13:02     ` Xi Ruoyao
2023-03-07 13:18       ` caiyinyu
2023-03-07 17:23         ` Noah Goldstein
2023-03-08  7:16           ` caiyinyu
2023-03-08 16:56             ` Noah Goldstein
2023-03-09  1:26               ` caiyinyu
2023-03-09  3:25                 ` Xi Ruoyao [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-01  3:22 caiyinyu
2023-03-01  4:19 ` Noah Goldstein
2023-03-01  9:10   ` caiyinyu
2023-03-01 16:42     ` Noah Goldstein
2023-03-01 17:33       ` H.J. Lu
2023-03-02  2:37       ` caiyinyu

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=e47cd4b0b2053b7c0a850c9b7e89e66bf8e97970.camel@xry111.site \
    --to=xry111@xry111.site \
    --cc=caiyinyu@loongson.cn \
    --cc=goldstein.w.n@gmail.com \
    --cc=hjl.tools@gmail.com \
    --cc=libc-alpha@sourceware.org \
    /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).