unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: ng0 <ng0@n0.is>
Cc: guix-devel@gnu.org
Subject: Re: 01/01: gnu: Add badass.
Date: Mon, 29 Jan 2018 18:09:16 -0500	[thread overview]
Message-ID: <87372ob6ub.fsf@netris.org> (raw)
In-Reply-To: <20180129215806.5F45C20512@vcs0.savannah.gnu.org> (Leo Famulari's message of "Mon, 29 Jan 2018 16:58:06 -0500 (EST)")

Hi ng0,

> commit 57f9671d22bb4ee37962c31b9eed0ae50859398a
> Author: ng0 <ng0@n0.is>
> Date:   Wed Jan 17 22:42:55 2018 +0000
>
>     gnu: Add badass.
[...]
> +  (package
> +    (name "badass")
> +    (version (git-version "0.0" revision commit))
[...]
> +    (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.")

Why do you think this belongs in Guix?  Do you intend to use it
yourself, or do you have reason to believe that Guix users would want
this?

There's a lot of garbage out there.  Guix doesn't need to include every
script that someone uploaded to github.  Frankly, I'm embarrassed to
have a package like this in Guix.

        Mark

       reply	other threads:[~2018-01-29 23:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180129215805.7086.26926@vcs0.savannah.gnu.org>
     [not found] ` <20180129215806.5F45C20512@vcs0.savannah.gnu.org>
2018-01-29 23:09   ` Mark H Weaver [this message]
2018-01-30  4:17     ` 01/01: gnu: Add badass Leo Famulari
2018-01-31 13:53       ` Package inclusion criteria Ludovic Courtès
2018-01-31 14:10         ` ng0
2018-01-31 17:56           ` myglc2
2018-01-31 23:48           ` Ludovic Courtès
2018-01-30  9:05     ` 01/01: gnu: Add badass ng0
2018-01-30  9:12       ` ng0
2018-01-31  3:54         ` Oleg Pykhalov

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=87372ob6ub.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=guix-devel@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).