all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: emacs-devel@gnu.org
Subject: Re: [emacs-announce] Emacs pretest 25.0.93
Date: Sun, 24 Apr 2016 08:56:44 +0300	[thread overview]
Message-ID: <83r3dv4kir.fsf@gnu.org> (raw)
In-Reply-To: <87a8kk0xzy.fsf@web.de> (message from Michael Heerdegen on Sun, 24 Apr 2016 00:19:13 +0200)

> From: Michael Heerdegen <michael_heerdegen@web.de>
> Date: Sun, 24 Apr 2016 00:19:13 +0200
> Cc: emacs-devel@gnu.org
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > IOW, you both build in the same directory from 2 different Git
> > branches, is that right?
> 
> I think so.  To make it clear: I had no problems with (building) Emacs
> itself.
> 
> I had Helm build with master.  Then I switched to emacs-25 and tried to
> upgrade Helm.  Helm's makefile calling `update-directory-autoloads' gave
> the error.

I don't think this can be done reliably without completely cleaning
your Git clone (with Git commands), in addition to "make distclean"
etc.  Emacs branches diverge too quickly for this to work (like it
does with some other projects); it's why I use two separate directory
trees to track both branches simultaneously.



  reply	other threads:[~2016-04-24  5:56 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-22 17:26 [emacs-announce] Emacs pretest 25.0.93 Nicolas Petton
2016-04-22 17:52 ` Philipp Stephani
2016-04-22 18:58 ` Eli Zaretskii
2016-04-22 19:08   ` nicolas
2016-04-22 19:12   ` Nicolas Petton
2016-04-22 19:58     ` Eli Zaretskii
2016-04-23 11:41 ` Achim Gratz
2016-04-23 12:05   ` Eli Zaretskii
2016-04-23 12:28     ` Achim Gratz
2016-04-23 12:37       ` Achim Gratz
2016-04-23 12:51         ` Eli Zaretskii
2016-04-23 13:29           ` Achim Gratz
2016-04-23 13:48             ` Eli Zaretskii
2016-04-23 15:20               ` Michael Heerdegen
2016-04-23 16:55                 ` Achim Gratz
2016-04-23 17:23                   ` Michael Heerdegen
2016-04-23 17:59                     ` Eli Zaretskii
2016-04-23 18:11                       ` Achim Gratz
2016-04-23 22:19                       ` Michael Heerdegen
2016-04-24  5:56                         ` Eli Zaretskii [this message]
2016-04-24  6:22                           ` Achim Gratz
2016-04-23 17:39                   ` Glenn Morris
2016-04-23 17:54                     ` Achim Gratz
2016-04-23 18:46                     ` Glenn Morris
2016-04-23 12:52       ` [emacs-announce] " Eli Zaretskii
2016-04-25 10:09 ` Phillip Lord
2016-04-25 10:21   ` Eli Zaretskii
2016-04-25 13:25     ` Chris Zheng
2016-04-26  5:45       ` Eli Zaretskii
2016-04-26 16:49         ` Phillip Lord
2016-04-26 17:26           ` Eli Zaretskii
2016-04-26 17:45             ` Phillip Lord
2016-04-26 18:29             ` Eli Zaretskii
2016-04-26 19:09               ` Kaushal Modi
2016-04-26 19:14                 ` Eli Zaretskii
2016-04-26 19:28                   ` Kaushal Modi
2016-04-26 19:32               ` Stephen Leake
2016-04-26 19:40                 ` Eli Zaretskii
2016-04-26 22:32                   ` Phillip Lord
2016-04-27  7:25                     ` Eli Zaretskii
2016-04-30  9:57                   ` Eli Zaretskii
2016-04-25 22:30     ` Phillip Lord
2016-04-26 13:43       ` Eli Zaretskii
2016-04-26 13:57         ` Kaushal Modi

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=83r3dv4kir.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=michael_heerdegen@web.de \
    /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.