public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Kito Cheng <kito.cheng@gmail.com>
To: Vineet Gupta <vineetg@rivosinc.com>
Cc: Palmer Dabbelt <palmer@rivosinc.com>,
	gcc-patches@gcc.gnu.org, jeffreyalaw@gmail.com,
	 gnu-toolchain@rivosinc.com, richard.sandiford@arm.com
Subject: Re: [PATCH] MAINTAINERS: add Vineet Gupta to write after approval
Date: Sat, 22 Apr 2023 00:03:04 +0800	[thread overview]
Message-ID: <CA+yXCZBoXFWJ5MAv2mZj6AfS8YuKAfGzZHuCn0oMzaRgtb+q9Q@mail.gmail.com> (raw)
In-Reply-To: <16f368e5-e9b2-f719-91ea-a4aeed9378b0@rivosinc.com>

You need use git+ssh protocol, I use this way to manage that:

git remote add upstream-write git+ssh://<username>@gcc.gnu.org/git/gcc.git
git push upstream-write master


On Sat, Apr 22, 2023 at 12:00 AM Vineet Gupta <vineetg@rivosinc.com> wrote:
>
>
> On 4/21/23 02:30, Richard Sandiford wrote:
> > No approval is needed when adding oneself to write-after-approval.
> > The fact that one's able to make the change is proof enough.
>
> Thx Richard.
>
> Noob question: I tried to commit/push but failed.
>
> | $ git remote show upstream
> | * remote upstream
> |  Fetch URL: git://gcc.gnu.org/git/gcc.git
> |
> | $ git push upstream upstream-exp:master
> | fatal: remote error: service not enabled: /git/gcc.git
>
> Reading thru [1] it seems commit on trunk is only possible via git svn.
> Is that true ?
>
> Thx,
> -Vineet
>
> [1] https://gcc.gnu.org/wiki/GitMirror

  reply	other threads:[~2023-04-21 16:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-20 16:55 Vineet Gupta
2023-04-20 17:31 ` Palmer Dabbelt
2023-04-21  9:30   ` Richard Sandiford
2023-04-21 16:00     ` Vineet Gupta
2023-04-21 16:03       ` Kito Cheng [this message]
2023-04-21 16:09         ` [committed] " Vineet Gupta

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+yXCZBoXFWJ5MAv2mZj6AfS8YuKAfGzZHuCn0oMzaRgtb+q9Q@mail.gmail.com \
    --to=kito.cheng@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gnu-toolchain@rivosinc.com \
    --cc=jeffreyalaw@gmail.com \
    --cc=palmer@rivosinc.com \
    --cc=richard.sandiford@arm.com \
    --cc=vineetg@rivosinc.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).