From: Kito Cheng <kito.cheng@gmail.com>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: juzhe.zhong@rivai.ai, jeffreyalaw@gmail.com, gcc-patches@gcc.gnu.org
Subject: Re: Re: [PATCH] RISC-V: Fix incorrect annotation
Date: Fri, 23 Dec 2022 13:47:02 +0800 [thread overview]
Message-ID: <CA+yXCZCgKGNSp_kGyBEfesNcOQAKEodD=3t1H3OjqztUeGg5RQ@mail.gmail.com> (raw)
In-Reply-To: <mhng-285a76ea-3525-45d4-8b5d-71723356437f@palmer-ri-x1c9a>
Committed, thanks :)
Ju-Zhe has not figured out how to commit to his environment yet, I am
helping him to set up.
On Wed, Dec 21, 2022 at 7:38 AM Palmer Dabbelt <palmer@dabbelt.com> wrote:
>
> On Tue, 20 Dec 2022 15:33:11 PST (-0800), juzhe.zhong@rivai.ai wrote:
> > Thanks. I received an email from sourceware:
> > "You should now have write access to the source control repository for your project."
> > It seems that I can merge codes? However, I still don't know how to merge codes.
>
> You should have a sourceware account, along with an associated private
> key. With those you should be able to get push access via
> https://gcc.gnu.org/gitwrite.html
>
> >
> >
> > juzhe.zhong@rivai.ai
> >
> > From: Jeff Law
> > Date: 2022-12-21 00:02
> > To: juzhe.zhong
> > CC: gcc-patches@gcc.gnu.org; kito.cheng@gmail.com; palmer@dabbelt.com
> > Subject: Re: [PATCH] RISC-V: Fix incorrect annotation
> >
> >
> > On 12/19/22 17:38, juzhe.zhong wrote:
> >> Would you mind merging it for me？ I can‘t merge code.
> > Do you mean you do not have write access to the repository? If so, that
> > can be easily fixed.
> >
> > https://sourceware.org/cgi-bin/pdw/ps_form.cgi
> >
> > List me as your sponsor.
> >
> > jeff
> >
prev parent reply other threads:[~2022-12-23 5:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 23:13 juzhe.zhong
2022-12-20 0:28 ` Jeff Law
[not found] ` <36D1C05330B9612D+065D340F-26F5-4844-8ACE-EA8091A41E6A@rivai.ai>
2022-12-20 16:02 ` Jeff Law
2022-12-20 16:06 ` Palmer Dabbelt
2022-12-20 16:15 ` Jeff Law
2022-12-20 23:33 ` 钟居哲
2022-12-20 23:38 ` Palmer Dabbelt
2022-12-23 5:47 ` Kito Cheng [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='CA+yXCZCgKGNSp_kGyBEfesNcOQAKEodD=3t1H3OjqztUeGg5RQ@mail.gmail.com' \
--to=kito.cheng@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=juzhe.zhong@rivai.ai \
--cc=palmer@dabbelt.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).