all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Rocky Bernstein <rocky@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: [elpa] master ecf1577 1/5: Avoid reading a binary as a source file
Date: Thu, 4 Aug 2016 09:52:30 -0400	[thread overview]
Message-ID: <CANCp2gaS-jd8QgAEVjvn3JgeMi0=2JVxUiPKzVDT7KdLcuZ_5Q@mail.gmail.com> (raw)
In-Reply-To: <jwvziotf8im.fsf-monnier+emacsdiffs@gnu.org>

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

Ok. Fixed in elpa now.

And that code improvement a while back to loc-changes using zerop, if you
could make, that'd be fine as well.

In general if you want to create push changes to elpa please do so. Or if
it's something you want to comment about make a branch and push to that.
Dealing with diffs via email is for me error prone.

On Thu, Aug 4, 2016 at 12:44 AM, Stefan Monnier <monnier@iro.umontreal.ca>
wrote:

> > -; (require 'term)
> > +;; (require 'term)
> > +(require 'files)
>
> Which "files" package is that?  The one that comes with Emacs is
> preloaded, so it never needs to be `required' explicitly.
>
>
>         Stefan
>

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

      reply	other threads:[~2016-08-04 13:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20160804030326.16920.78136@vcs.savannah.gnu.org>
     [not found] ` <20160804030326.B379D220169@vcs.savannah.gnu.org>
2016-08-04  4:43   ` [elpa] master d7bac58 3/5: Wrong require again Stefan Monnier
2016-08-04 13:45     ` Rocky Bernstein
2016-08-04 22:05       ` Stefan Monnier
2016-08-04 22:05         ` Rocky Bernstein
     [not found] ` <20160804030326.835FA2200F4@vcs.savannah.gnu.org>
2016-08-04  4:44   ` [elpa] master ecf1577 1/5: Avoid reading a binary as a source file Stefan Monnier
2016-08-04 13:52     ` Rocky Bernstein [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

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

  git send-email \
    --in-reply-to='CANCp2gaS-jd8QgAEVjvn3JgeMi0=2JVxUiPKzVDT7KdLcuZ_5Q@mail.gmail.com' \
    --to=rocky@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.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.