From: Leo Famulari <leo@famulari.name>
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: 27110@debbugs.gnu.org, Alex Griffin <a@ajgrf.com>
Subject: bug#27110: [PATCH] gnu: asciinema: Update to 1.4.0.
Date: Sun, 28 May 2017 14:37:53 -0400 [thread overview]
Message-ID: <20170528183753.GB15883@jasmine> (raw)
In-Reply-To: <1519f8c5.AEUAKk_HotIAAAAAAAAAAAPFk78AAAACwQwAAAAAAAW9WABZKwI9@mailjet.com>
[-- Attachment #1: Type: text/plain, Size: 655 bytes --]
On Sun, May 28, 2017 at 10:30:34PM +0530, Arun Isaac wrote:
>
> Thanks for the patch!
>
> > * gnu/packages/terminals.scm (asciinema): Update to 1.4.0.
> > [source]: Use pypi-uri.
>
> Could you switch to upstream's github release tarball instead?
> https://github.com/asciinema/asciinema/archive/v1.4.0.tar.gz
>
> LGTM, otherwise!
Is there a reason to prefer one over the other?
I ask because, typically, these unammed GitHub tarballs are not actual
releases prepared by the maintainers, but just a snapshot of the Git
repo, created automatically by GitHub for each tag. PyPi tends to
contain the "real" release in cases like this.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-05-28 18:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-28 1:16 bug#27110: [PATCH] gnu: asciinema: Update to 1.4.0 Alex Griffin
2017-05-28 17:00 ` Arun Isaac
2017-05-28 18:37 ` Leo Famulari [this message]
2017-05-28 22:18 ` Arun Isaac
[not found] ` <2dff1be8.ADsAAhu0Cj4AAAAAAAAAAAO8ccgAAAACwQwAAAAAAAW9WABZK0zP@mailjet.com>
2017-05-28 22:33 ` Leo Famulari
2017-05-28 23:01 ` Marius Bakke
2017-05-29 5:46 ` Arun Isaac
2017-05-29 17:26 ` Arun Isaac
2017-05-29 19:23 ` Arun Isaac
[not found] ` <a9d8e951.AEAAKtByx2QAAAAAAAAAAAO8ccgAAAACwQwAAAAAAAW9WABZLHUl@mailjet.com>
2017-05-29 20:42 ` Leo Famulari
2017-05-30 8:20 ` Arun Isaac
[not found] ` <be173c52.AEMAK1ybgp8AAAAAAAAAAAPFd4cAAAACwQwAAAAAAAW9WABZLStT@mailjet.com>
2017-05-30 15:10 ` Marius Bakke
2017-05-30 16:06 ` Arun Isaac
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=20170528183753.GB15883@jasmine \
--to=leo@famulari.name \
--cc=27110@debbugs.gnu.org \
--cc=a@ajgrf.com \
--cc=arunisaac@systemreboot.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.