From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: 26274@debbugs.gnu.org, npostavs@users.sourceforge.net
Subject: bug#26274: 26.0.50; completion regression
Date: Wed, 29 Mar 2017 21:33:57 +0300 [thread overview]
Message-ID: <83zig453vu.fsf@gnu.org> (raw)
In-Reply-To: <87h92cym36.fsf@rosalinde> (message from Stephen Berman on Wed, 29 Mar 2017 20:27:57 +0200)
> From: Stephen Berman <stephen.berman@gmx.net>
> Cc: 26274@debbugs.gnu.org, Noam Postavsky <npostavs@users.sourceforge.net>
> Date: Wed, 29 Mar 2017 20:27:57 +0200
>
> My guess is the first of these, since it's between the bad and good
> builds; the other two commits are much earlier. But given the above
> make failure, I don't know how to build that commit (or the one before
> it).
You could clone the repository anew, checkout that commit, and then
build.
next prev parent reply other threads:[~2017-03-29 18:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 10:56 bug#26274: 26.0.50; completion regression Stephen Berman
2017-03-27 16:22 ` Stephen Berman
2017-03-29 17:00 ` Stephen Berman
2017-03-29 17:27 ` Eli Zaretskii
2017-03-29 18:27 ` Stephen Berman
2017-03-29 18:33 ` Eli Zaretskii [this message]
2017-03-29 18:43 ` Stephen Berman
2017-03-29 18:49 ` Noam Postavsky
2017-03-29 20:00 ` Stephen Berman
2017-03-30 2:33 ` Eli Zaretskii
2017-03-30 13:38 ` Michal Nazarewicz
2017-03-30 14:17 ` Michal Nazarewicz
2017-03-30 14:30 ` Michal Nazarewicz
2017-03-30 16:18 ` Michal Nazarewicz
2017-03-30 18:02 ` Stephen Berman
2017-03-30 19:11 ` Michal Nazarewicz
2017-03-30 20:14 ` Stephen Berman
2017-03-30 18:06 ` Eli Zaretskii
2017-04-06 18:58 ` Michal Nazarewicz
2017-04-07 8:37 ` Stephen Berman
2017-03-29 17:28 ` Noam Postavsky
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=83zig453vu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=26274@debbugs.gnu.org \
--cc=npostavs@users.sourceforge.net \
--cc=stephen.berman@gmx.net \
/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.