From: "Frank Ch. Eigler" <fche@redhat.com>
To: Overseers mailing list <overseers@sourceware.org>
Cc: overseers@gcc.gnu.org, Georg-Johann Lay <avr@gjlay.de>
Subject: Re: Help with git write access.
Date: Thu, 18 May 2023 09:22:49 -0400 [thread overview]
Message-ID: <20230518132249.GA3026@redhat.com> (raw)
In-Reply-To: <bff8255c-c871-f724-68f3-7e97c371a40c@gjlay.de>
Hi -
> [...]
> So I have a bunch of questions and need some help.
It sounds like you've found <https://gcc.gnu.org/gitwrite.html>, and
further questions with project-specific advice should go to
<gcc@gcc.gnu.org>. (Overseers can help with ssh key authentication
issues.)
- FChE
prev parent reply other threads:[~2023-05-18 13:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-18 13:09 Georg-Johann Lay
2023-05-18 13:22 ` Frank Ch. Eigler [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=20230518132249.GA3026@redhat.com \
--to=fche@redhat.com \
--cc=avr@gjlay.de \
--cc=overseers@gcc.gnu.org \
--cc=overseers@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).