From: Eli Zaretskii <eliz@gnu.org>
To: Sam Halliday <sam.halliday@gmail.com>
Cc: 19983@debbugs.gnu.org
Subject: bug#19983: 24.4; exit-emacs regression in 24.4?
Date: Tue, 10 Mar 2015 20:57:53 +0200 [thread overview]
Message-ID: <837fuo65ou.fsf@gnu.org> (raw)
In-Reply-To: <87a8znumft.fsf@gmail.com>
> From: Sam Halliday <sam.halliday@gmail.com>
> Cc: 19983@debbugs.gnu.org
> Date: Sun, 08 Mar 2015 22:57:42 +0000
>
> Eli Zaretskii <eliz@gnu.org> writes:
> >> Hmm. I might try setting up a disectian of the emacs commits
> > Thanks, that will be useful indeed.
>
> 5f53d2441abf6eafe8e14f29d73e14afe8bec35f is the first bad commit
> commit 5f53d2441abf6eafe8e14f29d73e14afe8bec35f
> Author: HIROSHI OOTA <nil@mad.dog.cx>
> Date: Wed Jan 25 13:35:05 2012 +0800
>
> * src/coding.c (encode_designation_at_bol): Change return value to EMACS_INT.
>
>
> But this may be only an approximation, as there are a few commits where
> it is not possible to compile emacs and in those cases I flagged them as
> "good".
Can you show the two commits, a "bad" one and a "good" one, around
5f53d2441abf6eafe8e14f29d73e14afe8bec35f, such that you actually built
and tested those two?
Thanks.
next prev parent reply other threads:[~2015-03-10 18:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-02 22:38 bug#19983: 24.4; exit-emacs regression in 24.4? Sam Halliday
2015-03-03 15:38 ` Eli Zaretskii
[not found] ` <87k2yrvea4.fsf@gmail.com>
2015-03-08 16:14 ` Eli Zaretskii
2015-03-08 16:26 ` Sam Halliday
2015-03-08 16:31 ` Eli Zaretskii
2015-03-08 18:34 ` Sam Halliday
2015-03-08 20:17 ` Eli Zaretskii
2015-03-08 19:11 ` Sam Halliday
2015-03-08 20:18 ` Eli Zaretskii
2015-03-08 22:57 ` Sam Halliday
2015-03-09 3:16 ` Óscar Fuentes
2015-03-10 18:57 ` Eli Zaretskii [this message]
2015-03-10 19:30 ` Glenn Morris
2015-03-10 19:42 ` Sam Halliday
2015-03-10 23:17 ` Sam Halliday
2015-03-11 16:07 ` Eli Zaretskii
2015-03-11 17:44 ` Glenn Morris
2015-03-13 0:47 ` Sam Halliday
2015-03-13 6:24 ` Glenn Morris
2015-03-13 8:30 ` Andreas Schwab
2015-03-14 10:36 ` Sam Halliday
2015-03-22 20:00 ` Sam Halliday
2015-03-10 20:53 ` Andreas Schwab
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=837fuo65ou.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=19983@debbugs.gnu.org \
--cc=sam.halliday@gmail.com \
/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).