unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Sebastien Vauban <sva-news@mygooglest.com>
Cc: 18448@debbugs.gnu.org
Subject: bug#18448: Problems installing (M)ELPA packages
Date: Thu, 11 Sep 2014 11:53:39 -0400	[thread overview]
Message-ID: <esppf217cs.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <86iokubntn.fsf@somewhere.org> (Sebastien Vauban's message of "Thu, 11 Sep 2014 09:47:48 +0200")

Sebastien Vauban wrote:

> (This discussion was started on gnu.emacs.help)

It would be nice if your report could have summarized the issue.

Anyway, this is a duplicate of http://debbugs.gnu.org/18443,
which is a duplicate of http://debbugs.gnu.org/10125.





      reply	other threads:[~2014-09-11 15:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-11  7:47 bug#18448: Problems installing (M)ELPA packages Sebastien Vauban
2014-09-11 15:53 ` Glenn Morris [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://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=esppf217cs.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=18448@debbugs.gnu.org \
    --cc=sva-news@mygooglest.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/emacs.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).