From: Leo Famulari <leo@famulari.name>
To: swedebugia <swedebugia@riseup.net>
Cc: 34896@debbugs.gnu.org
Subject: bug#34896: Add "game" to end of synopsis of openttd
Date: Sun, 17 Mar 2019 14:08:59 -0400 [thread overview]
Message-ID: <20190317180859.GB1410@jasmine.lan> (raw)
In-Reply-To: <b98a5af7-ef8a-cc62-9288-d5d7b9f33d4f@riseup.net>
[-- Attachment #1: Type: text/plain, Size: 241 bytes --]
On Sun, Mar 17, 2019 at 05:45:47PM +0100, swedebugia wrote:
> It currently says "Transportation economics simulator"
>
> This addition makes it easier to find. e.g. with 'guix package -A game'
Okay! Would you like to submit a patch?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-03-17 18:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-17 16:45 bug#34896: Add "game" to end of synopsis of openttd swedebugia
2019-03-17 18:08 ` Leo Famulari [this message]
2019-03-17 20:53 ` swedebugia
2019-03-18 16:12 ` Leo Famulari
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=20190317180859.GB1410@jasmine.lan \
--to=leo@famulari.name \
--cc=34896@debbugs.gnu.org \
--cc=swedebugia@riseup.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).