From: "Ludovic Courtès" <ludo@gnu.org>
To: Vagrant Cascadian <vagrant@reproducible-builds.org>
Cc: Guix-devel <Guix-devel@gnu.org>
Subject: Re: savannah access (was Re: [bug#35478] [PATCH] gnu: diffoscope: Update to 114.)
Date: Tue, 30 Apr 2019 14:52:00 +0200 [thread overview]
Message-ID: <87tveflkpb.fsf@gnu.org> (raw)
In-Reply-To: <87k1fcw4p5.fsf@ponder> (Vagrant Cascadian's message of "Mon, 29 Apr 2019 20:29:58 -0700")
[-- Attachment #1: Type: text/plain, Size: 981 bytes --]
Hi Vagrant!
(Please keep the list Cc’d.)
Vagrant Cascadian <vagrant@reproducible-builds.org> skribis:
> On 2019-04-29, Ludovic Courtès wrote:
>> Vagrant Cascadian <vagrant@reproducible-builds.org> skribis:
>>> * gnu/packages/package-management (diffoscope): Update to 114.
>>
>> Applied, thanks!
>>
>> Would you like to create an account on Savannah? We’d add you to the
>> ‘guix’ group, which would make it easier for you to push changes like
>> this one or in your other areas of expertise.
>
> Sure. I just created "vagrantc" on savannah.gnu.org, and uploaded my ssh
> and gpg keys. Thanks for the sign of trust!
Awesome, I’ve added you to the group so it should now work. Please read
‘HACKING’ for the conventions that apply to commit access.
Could yous send a reply this message signed with the key you’ll use for
commits so that everyone can establish the mapping?
Thanks for your work, and welcome aboard! :-)
Ludo’.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next parent reply other threads:[~2019-04-30 12:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87r29lc3w8.fsf@ponder>
[not found] ` <87bm0pjm9u.fsf@gnu.org>
[not found] ` <87k1fcw4p5.fsf@ponder>
2019-04-30 12:52 ` Ludovic Courtès [this message]
2019-04-30 17:12 ` savannah access (was Re: [bug#35478] [PATCH] gnu: diffoscope: Update to 114.) Vagrant Cascadian
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tveflkpb.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=Guix-devel@gnu.org \
--cc=vagrant@reproducible-builds.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).