all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Chris Marusich <cmmarusich@gmail.com>
Cc: rekado@elephly.net, 28509@debbugs.gnu.org, bavier@member.fsf.org
Subject: [bug#28509] [PATCH 1/1] gnu: Add GnuCash documentation.
Date: Thu, 12 Oct 2017 10:00:31 +0200	[thread overview]
Message-ID: <87po9sre1s.fsf@gnu.org> (raw)
In-Reply-To: <87k201awtg.fsf@gmail.com> (Chris Marusich's message of "Wed, 11 Oct 2017 20:07:07 -0700")

[-- Attachment #1: Type: text/plain, Size: 784 bytes --]

Hi Chris,

Chris Marusich <cmmarusich@gmail.com> skribis:

> ludo@gnu.org (Ludovic Courtès) writes:
>
>> Can you create an account on savannah.gnu.org, and email it here?
>> Please add the OpenPGP key that you’ll use to sign commits to your
>> account info, and reply with a message signed with that key.
>
> I've created an account and uploaded the key.  The info is here:
>
>   Profile: https://savannah.gnu.org/users/marusich
>   Key fingerprint: CBF5 9755 CBE7 E7EF EF18  3FB1 DD40 9A15 D822 469D
>
> I'll try committing the change once you let me know I've been given
> access.  Thank you!

I’ve added you so you should be able to commit now.

Please (re)read ‘HACKING’ for rules and tips regarding commit access.

Welcome again!  :-)

Ludo’.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2017-10-12  8:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-19  9:10 [bug#28509] [PATCH 0/1] gnu: Add GnuCash documentation Chris Marusich
2017-09-19  9:10 ` [bug#28509] [PATCH 1/1] " Chris Marusich
2017-09-19 12:02   ` Ludovic Courtès
2017-10-07 20:48     ` Ludovic Courtès
2017-10-08 23:43       ` Chris Marusich
2017-10-09  7:30         ` Ludovic Courtès
2017-10-12  3:07           ` Chris Marusich
2017-10-12  8:00             ` Ludovic Courtès [this message]
2017-10-13 19:47             ` bug#28509: " 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87po9sre1s.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=28509@debbugs.gnu.org \
    --cc=bavier@member.fsf.org \
    --cc=cmmarusich@gmail.com \
    --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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.