From: Arun Isaac <arunisaac@systemreboot.net>
To: "Ludovic Courtès" <ludo@gnu.org>,
"Sohom Bhattacharjee" <soham.bhattacharjee15@gmail.com>
Cc: 31004-done@debbugs.gnu.org
Subject: [bug#31004] [PATCH] gnu: Add emacs-anzu
Date: Sat, 31 Mar 2018 23:06:01 +0530 [thread overview]
Message-ID: <cu7h8owf8qm.fsf@systemreboot.net> (raw)
In-Reply-To: <87y3i8i2h4.fsf@gnu.org>
Ludovic Courtès <ludo@gnu.org> writes:
> (origin
> (method url-fetch)
> (uri (string-append "http://stable.melpa.org/packages/anzu-"
> version ".el"))
Hi Ludo,
Shouldn't we be using the upstream Github release tarball? Do we accept
MELPA now?
next prev parent reply other threads:[~2018-03-31 17:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-31 14:50 [bug#31004] [PATCH] gnu: Add emacs-anzu Sohom Bhattacharjee
2018-03-31 17:23 ` bug#31004: " Ludovic Courtès
2018-03-31 17:36 ` Arun Isaac [this message]
2018-03-31 20:13 ` [bug#31004] " Ludovic Courtès
2018-04-01 11:40 ` Sohom Bhattacharjee
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=cu7h8owf8qm.fsf@systemreboot.net \
--to=arunisaac@systemreboot.net \
--cc=31004-done@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=soham.bhattacharjee15@gmail.com \
/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).