From: Mark Wielaard <mark@klomp.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: Patrick Monnerat <patrick@monnerat.net>, Simon Marchi <simark@simark.ca>
Subject: Re: Git push access request to the binutils-gdb repository
Date: Mon, 25 Jul 2022 13:41:14 +0200 [thread overview]
Message-ID: <e23d8a2708f9e98ea1d1d251f3e7f3370c3bea3c.camel@klomp.org> (raw)
In-Reply-To: <55d63e63-a1ba-bc72-c36e-d6ef046e1f62@monnerat.net>
Hi Patrick,
On Mon, 2022-07-25 at 10:45 +0200, Patrick Monnerat via Overseers
wrote:
> In accordance with Simon Marchi, I kindly request you to grant me
> push access on the binutils-gdb repository. See
> https://sourceware.org/pipermail/gdb-patches/2022-July/191043.html.
>
> As an Insight maintainer, I already have an account on sourceware.org
> with login monnerat@sourceware.org.
It turns out you already belong to the "src" group which should allow
you to push commits to the binutils-gdb.git repo.
Please let us know if anything doesn't work as expected.
Cheers,
Mark
prev parent reply other threads:[~2022-07-25 11:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-25 8:45 Patrick Monnerat
2022-07-25 11:41 ` Mark Wielaard [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=e23d8a2708f9e98ea1d1d251f3e7f3370c3bea3c.camel@klomp.org \
--to=mark@klomp.org \
--cc=overseers@sourceware.org \
--cc=patrick@monnerat.net \
--cc=simark@simark.ca \
/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).