unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Sohom Bhattacharjee <soham.bhattacharjee15@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 31004-done@debbugs.gnu.org
Subject: [bug#31004] [PATCH] gnu: Add emacs-anzu
Date: Sun, 01 Apr 2018 11:40:57 +0000	[thread overview]
Message-ID: <CAE2ctpGRciV+X3Jxc6CQhhdMVjiwqE8ms=7CE3rzQ6aY6j_dew@mail.gmail.com> (raw)
In-Reply-To: <87muyohuko.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 903 bytes --]

Okay! I will get to it within a day!!

Thanks! :)

On Sun 1 Apr, 2018, 01:43 Ludovic Courtès, <ludo@gnu.org> wrote:

> Hello,
>
> Arun Isaac <arunisaac@systemreboot.net> skribis:
>
> > 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?
>
> Arf, you’re right!
>
> Sohom, the problem Arun is referring to is that stable.melpa.org
> eventually removes source code.  Thus we usually refer to the upstream
> repository instead.
>
> Could you try to make this change?  You can look for examples in
> emacs.scm.  Feel free to ask if anything’s unclear.
>
> Thanks in advance!
>
> Ludo’.
>

[-- Attachment #2: Type: text/html, Size: 1678 bytes --]

      reply	other threads:[~2018-04-01 11:42 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   ` [bug#31004] " Arun Isaac
2018-03-31 20:13     ` Ludovic Courtès
2018-04-01 11:40       ` Sohom Bhattacharjee [this message]

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='CAE2ctpGRciV+X3Jxc6CQhhdMVjiwqE8ms=7CE3rzQ6aY6j_dew@mail.gmail.com' \
    --to=soham.bhattacharjee15@gmail.com \
    --cc=31004-done@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    /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).