all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: 16901@debbugs.gnu.org, dmantipov@yandex.ru
Subject: bug#16901: 24.3.50; emacs_backtrace.txt
Date: Sat, 01 Mar 2014 09:15:41 +0200	[thread overview]
Message-ID: <83y50uv17m.fsf@gnu.org> (raw)
In-Reply-To: <CAAeL0SRsO74PW6SqBPOXEy4OTuH4R4MrfwrpthkdT8s=s6oaDw@mail.gmail.com>

> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Fri, 28 Feb 2014 18:12:57 +0100
> Cc: Eli Zaretskii <eliz@gnu.org>, Dmitry Antipov <dmantipov@yandex.ru>, 16901@debbugs.gnu.org
> 
> > Maybe some development
> > just before that build is responsible?
> 
> These are the changes between the previous snapshot and the build from
> Feb 22, except for the ones obviously unrelated (doc fixes, manual,
> tests, etc.).

Thanks; I see nothing that immediately stands out.  It could be an
unrelated change which just exposed a bug that was present previously.

Or it could be some change in Drew's use patterns, like in the
window/frame configurations and other customizations, which exposed an
extant bug.  Or even some changes in the OS and other programs used in
conjunction with Emacs, for that matter.

IOW, there's no way to be certain without a recipe, or something like
that.





  reply	other threads:[~2014-03-01  7:15 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<5d9f431d-d0c3-4cfa-b9e5-07cdf6718d5a@default>
     [not found] ` <<CAAeL0SRkM1gmNDJXkkrgZTCVohhGZeGgkyNDTojFx1GfzvM4RA@mail.gmail.com>
     [not found]   ` <<83mwhbwm9j.fsf@gnu.org>
     [not found]     ` <<53107F45.3060502@yandex.ru>
     [not found]       ` <<83d2i7wbyc.fsf@gnu.org>
2014-02-28 16:00         ` bug#16901: 24.3.50; emacs_backtrace.txt Drew Adams
2014-02-28 17:12           ` Juanma Barranquero
2014-03-01  7:15             ` Eli Zaretskii [this message]
     [not found] <<b93ed3b6-293d-44cd-959a-3933ccb4bcae@default>
     [not found] ` <<831tylvkq2.fsf@gnu.org>
2014-03-01 18:40   ` Drew Adams
     [not found] <<e42ac7ca-f017-406a-a5f5-a3dd6e096e4e@default>
     [not found] ` <<CAAeL0SRsO74PW6SqBPOXEy4OTuH4R4MrfwrpthkdT8s=s6oaDw@mail.gmail.com>
     [not found]   ` <<83y50uv17m.fsf@gnu.org>
2014-03-01 17:42     ` Drew Adams
2014-03-01 18:26       ` Eli Zaretskii
2014-03-02  4:16         ` Juanma Barranquero
2014-03-02 17:00           ` Eli Zaretskii
2014-03-02 20:45             ` Juanma Barranquero
2014-03-03 16:54             ` Eli Zaretskii
2014-03-03 17:28               ` Juanma Barranquero
2014-03-03 17:42                 ` Eli Zaretskii
2014-03-03 17:57                   ` Juanma Barranquero
2014-03-03 23:20               ` Ken Brown
2014-03-04  3:45                 ` Eli Zaretskii
2014-03-04 14:23                   ` Ken Brown
2014-03-04 17:37                     ` Eli Zaretskii
2014-03-04 19:04                       ` Ken Brown
2014-02-28  4:56 Drew Adams
2014-02-28  9:41 ` Juanma Barranquero
2014-02-28 10:43   ` Eli Zaretskii
2014-02-28 10:48     ` Juanma Barranquero
2014-02-28 11:41       ` Eli Zaretskii
2014-02-28 12:27         ` Juanma Barranquero
2014-02-28 15:00       ` Drew Adams
2014-02-28 12:21     ` Dmitry Antipov
2014-02-28 14:26       ` Eli Zaretskii
2014-02-28 15:44         ` Dmitry Antipov
2014-02-28 21:12           ` Paul Eggert
2014-03-01  8:47           ` Eli Zaretskii
2014-03-01  8:47           ` Eli Zaretskii
2014-03-01 10:12             ` Juanma Barranquero
2014-03-01 10:12             ` Juanma Barranquero
2014-03-01 10:46               ` Juanma Barranquero
2014-03-01 11:57                 ` Eli Zaretskii
2014-03-01 13:12                   ` Juanma Barranquero
2014-03-01 13:12                   ` Juanma Barranquero
2014-03-01 11:57                 ` Eli Zaretskii
2014-03-01 10:46               ` Juanma Barranquero
2014-03-20 18:31           ` Eli Zaretskii
2014-02-28 15:44         ` Dmitry Antipov

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=83y50uv17m.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=16901@debbugs.gnu.org \
    --cc=dmantipov@yandex.ru \
    --cc=lekktu@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 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.