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: Mon, 09 Oct 2017 09:30:40 +0200 [thread overview]
Message-ID: <871smcbwwv.fsf@gnu.org> (raw)
In-Reply-To: <87bmlhi4td.fsf@gmail.com> (Chris Marusich's message of "Sun, 08 Oct 2017 16:43:26 -0700")
Hi Chris,
Chris Marusich <cmmarusich@gmail.com> skribis:
> ludo@gnu.org (Ludovic Courtès) writes:
>
>> ludo@gnu.org (Ludovic Courtès) skribis:
>>
>>> Chris Marusich <cmmarusich@gmail.com> skribis:
>>>
>>>> * gnu/packages/gnucash.scm (gnucash-docs): Add it.
>>>> (gnucash): Use the glib-or-gtk-build-system, create a "doc" output, and
>>>> install the output of "gnucash-docs" into there.
>>>
>>> LGTM, thanks for working on it!
>>
>> Ping! :-)
>>
>> Ludo'.
>
> I'm waiting for someone with commit access to commit this. I don't have
> commit access. Would it be faster now and in the future if I just got
> commit access? I don't intend to commit anything without first
> reviewing it with the list - but I don't mind either way, so please let
> me know.
Oops, I was pretty sure you already had commit access, apologies!
So, let’s fix that. 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.
TIA!
Ludo’.
next prev parent reply other threads:[~2017-10-09 7:32 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 [this message]
2017-10-12 3:07 ` Chris Marusich
2017-10-12 8:00 ` Ludovic Courtès
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
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=871smcbwwv.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 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).