From: ludo@gnu.org (Ludovic Courtès)
To: Christopher Baines <mail@cbaines.net>
Cc: Ricardo Wurmus <rekado@elephly.net>, 27233@debbugs.gnu.org
Subject: [bug#27233] [PATCH] gnu: Add emacs-inf-ruby
Date: Fri, 16 Jun 2017 16:54:04 +0200 [thread overview]
Message-ID: <87mv98dlv7.fsf@gnu.org> (raw)
In-Reply-To: <7eebd181-88eb-4ff5-6184-d94fe9dbb79c@cbaines.net> (Christopher Baines's message of "Fri, 16 Jun 2017 14:54:48 +0100")
[-- Attachment #1: Type: text/plain, Size: 925 bytes --]
Christopher Baines <mail@cbaines.net> skribis:
> On 16/06/17 14:21, Ludovic Courtès wrote:
>> Howdy!
>>
>> Alex Kost <alezost@gmail.com> skribis:
>>
>>> If you would like to be able to push commits yourself, I'm sure Ludovic
>>> or Ricardo will provide you these rights :-)
>>
>> I think I proposed it before, or at least I thought about it. Anyway,
>> what’s your Savannah account Christopher? :-)
>
> I did get a message on IRC, but I missed it by a few days. My Savannah
> account username is cbaines.
Awesome, I’ve added you. Could you reply to this message, signed with
the OpenPGP key that you’ll use to sign commit (which presumably is the
one you uploaded at <https://savannah.gnu.org/users/cbaines>)?
After that please make sure to (re)read ‘HACKING’ and you’ll be all set.
Thank you, and “welcome” if that’s something we can say to an old timer!
;-)
Ludo’.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-06-16 14:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-04 12:53 bug#27233: [PATCH] gnu: Add emacs-inf-ruby Christopher Baines
2017-06-04 17:40 ` Leo Famulari
2017-06-16 13:13 ` Alex Kost
2017-06-16 13:21 ` [bug#27233] " Ludovic Courtès
2017-06-16 13:54 ` Christopher Baines
2017-06-16 14:54 ` Ludovic Courtès [this message]
2017-06-16 16:23 ` Christopher Baines
2017-06-16 13:51 ` Christopher Baines
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=87mv98dlv7.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=27233@debbugs.gnu.org \
--cc=mail@cbaines.net \
--cc=rekado@elephly.net \
/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).