unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Alex Kost <alezost@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 1/5] gnu: Add emacs-ht.
Date: Fri, 27 Jan 2017 04:59:29 -0500	[thread overview]
Message-ID: <20170127095929.GA28279@jasmine> (raw)
In-Reply-To: <87efzooo41.fsf@gmail.com>

On Fri, Jan 27, 2017 at 12:20:46PM +0300, Alex Kost wrote:
> Mathieu Othacehe (2017-01-26 13:31 +0100) wrote:
> > +      (uri (string-append
> > +             "http://melpa.org/packages/ht-"
> > +             version
> > +             ".el"))
> 
> We can't use files from melpa.org because once a new commit appears in
> the upstream repo, melpa will rebuilt the package and remove the
> previous version, so this package will lost its source and will not be
> buildable anymore.  So please use the latest available tarballs instead.

I think the linter should warn about this. It seems like you have to
send this email often.

  reply	other threads:[~2017-01-27  9:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-26 12:31 [PATCH 0/5] Add emacs-mu4e-alert Mathieu Othacehe
2017-01-26 12:31 ` [PATCH 1/5] gnu: Add emacs-ht Mathieu Othacehe
2017-01-27  9:20   ` Alex Kost
2017-01-27  9:59     ` Leo Famulari [this message]
2017-01-27 10:16       ` Mathieu OTHACEHE
2017-01-27 19:56         ` Alex Kost
2017-01-27 23:16           ` Ludovic Courtès
2017-01-28  8:18             ` Alex Kost
2017-01-28  9:07             ` Mathieu OTHACEHE
2017-01-30  9:09               ` ELPA importer and upstream URLs Ludovic Courtès
2017-01-30 15:57                 ` Mathieu OTHACEHE
2017-01-28 22:07             ` [PATCH 1/5] gnu: Add emacs-ht Carlo Zancanaro
2017-01-26 12:31 ` [PATCH 2/5] gnu: Add emacs-log4e Mathieu Othacehe
2017-01-26 12:31 ` [PATCH 3/5] gnu: Add emacs-gntp Mathieu Othacehe
2017-01-26 12:31 ` [PATCH 4/5] gnu: Add emacs-alert Mathieu Othacehe
2017-01-26 12:31 ` [PATCH 5/5] gnu: Add emacs-mu4e-alert Mathieu Othacehe

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=20170127095929.GA28279@jasmine \
    --to=leo@famulari.name \
    --cc=alezost@gmail.com \
    --cc=guix-devel@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).