From: Glenn Morris <rgm@gnu.org>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs pretest 25.0.93
Date: Sat, 23 Apr 2016 13:39:10 -0400 [thread overview]
Message-ID: <kh7ffotebl.fsf_-_@fencepost.gnu.org> (raw)
In-Reply-To: <87inz8nu39.fsf@Rainer.invalid> (Achim Gratz's message of "Sat, 23 Apr 2016 18:55:06 +0200")
Achim Gratz wrote:
> The reason for why there was no proper timestamp on these entries was
> that during my last build on 3rd of April I built also an EMacs from
> master and that build destroys trhe time-stamps that emacs-25 so
> desperately needs. Really, if there's something wrong with a file the
> build can re-create, it should not error out. Plus, there really needs
> to be some Makefile target to really clean up (no, 'make distclean'
> didn't do it). Plus, the fact that the lisp directory is shared
> between different builds and doesn't contain just the sources doesn't
> really help, either.
Ie, you switched in place from master to the release branch without
cleaning up first. You can't expect this to work. An older branch cannot
reliably clean-up for a newer branch.
Please take the emacs-announce keyword out of the subject (future
announcements should use Keyword: instead to avoid this), since this
whole chain is not an announcement. It's not even related to the
pretest, since you built from git, not the pretest.
next prev parent reply other threads:[~2016-04-23 17:39 UTC|newest]
Thread overview: 53+ 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
2016-04-24 6:22 ` Achim Gratz
2016-04-23 17:39 ` Glenn Morris [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2016-04-26 14:26 Angelo Graziosi
2016-04-26 16:06 ` Kaushal Modi
2016-04-26 16:23 ` Eli Zaretskii
2016-04-26 16:31 ` Eli Zaretskii
2016-04-26 16:44 ` Eli Zaretskii
2016-04-26 16:49 ` Kaushal Modi
2016-04-27 8:52 ` Angelo Graziosi
2016-04-27 9:21 ` Eli Zaretskii
2016-04-26 19:54 ` Angelo Graziosi
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=kh7ffotebl.fsf_-_@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=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).