From: Vagrant Cascadian <vagrant@reproducible-builds.org>
To: "Ludovic Courtès" <ludo@gnu.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 10:12:59 -0700 [thread overview]
Message-ID: <87y33rben8.fsf@ponder> (raw)
In-Reply-To: <87tveflkpb.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1111 bytes --]
On 2019-04-30, Ludovic Courtès wrote:
> 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.
Read it and looks reasonable to me.
> Could yous send a reply this message signed with the key you’ll use for
> commits so that everyone can establish the mapping?
Hello GNU Guix world!
> Thanks for your work, and welcome aboard! :-)
Thanks for the great welcome!
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
prev parent reply other threads:[~2019-04-30 17:13 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 ` savannah access (was Re: [bug#35478] [PATCH] gnu: diffoscope: Update to 114.) Ludovic Courtès
2019-04-30 17:12 ` Vagrant Cascadian [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
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=87y33rben8.fsf@ponder \
--to=vagrant@reproducible-builds.org \
--cc=Guix-devel@gnu.org \
--cc=ludo@gnu.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).