unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-devel@gnu.org
Subject: Re: [emacs-announce] Emacs pretest 25.0.93
Date: Sat, 23 Apr 2016 20:11:19 +0200	[thread overview]
Message-ID: <87a8kknqk8.fsf@Rainer.invalid> (raw)
In-Reply-To: 83twis4364.fsf@gnu.org

Eli Zaretskii writes:
> IOW, you both build in the same directory from 2 different Git
> branches, is that right?

No, I built emacs-25 in build-25 and master in build-master.  But it's
all for naught anyway because the build doesn't put all build products
into the build dirs.  You actually need to do a 'make extraclean', but
I'm rather going to build in-tree and use git-worktree instead, that
seems easier to me.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds




  reply	other threads:[~2016-04-23 18:11 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 [this message]
2016-04-23 22:19                       ` Michael Heerdegen
2016-04-24  5:56                         ` Eli Zaretskii
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

  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=87a8kknqk8.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=emacs-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/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).