From: Leo Famulari <leo@famulari.name>
To: ng0 <ng0@n0.is>
Cc: 30150@debbugs.gnu.org
Subject: [bug#30150] github-com-umayr-badass (or short: badass)
Date: Wed, 17 Jan 2018 15:17:45 -0800 [thread overview]
Message-ID: <20180117231745.GA16400@jasmine.lan> (raw)
In-Reply-To: <20180117224842.gfstulzpvxvf2dms@abyayala>
[-- Attachment #1: Type: text/plain, Size: 1069 bytes --]
On Wed, Jan 17, 2018 at 10:48:42PM +0000, ng0 wrote:
> From 23242a1b6b96fed99f2dea3567b95ef35e2ebe5b Mon Sep 17 00:00:00 2001
> From: ng0 <ng0@n0.is>
> Date: Wed, 17 Jan 2018 22:42:55 +0000
> Subject: [PATCH] gnu: Add github-com-umayr-badass.
>
> * gnu/packages/games.scm (github-com-umayr-badass): New variable.
[...]
> +(define-public go-github-com-umayr-badass
> + (let ((commit "3c3cd669b4fc8f73a102e3702788f7b28dc47dbb")
> + (revision "0"))
> + (package
> + (name "go-github-com-umayr-badass")
The name in the commit message is missing the 'go-' prefix.
> + (synopsis "Hacking contribution graphs in git")
> + (description
> + "Badass generates false commits for a range of dates, essentially
> +hacking the gamification of contribution graphs on platforms such as
> +Github or Gitlab.")
Hahaha, LGTM overall.
Only question is, should we call the package "badass"? I think the
long Go library names are only necessary for libraries, while we can
use a shorter name for an executable program like this one.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-01-17 23:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 22:48 [bug#30150] github-com-umayr-badass (or short: badass) ng0
2018-01-17 23:17 ` Leo Famulari [this message]
2018-01-18 8:17 ` ng0
2018-01-18 17:08 ` Leo Famulari
2018-01-18 17:45 ` Tobias Geerinckx-Rice
2018-01-27 18:35 ` ng0
2018-01-29 21:58 ` bug#30150: " 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=20180117231745.GA16400@jasmine.lan \
--to=leo@famulari.name \
--cc=30150@debbugs.gnu.org \
--cc=ng0@n0.is \
/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).