From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: 12074@debbugs.gnu.org, nicholas.dokos@hp.com
Subject: bug#12074: emacs crashes on startup
Date: Sat, 28 Jul 2012 20:32:31 +0300 [thread overview]
Message-ID: <83pq7fhjv4.fsf@gnu.org> (raw)
In-Reply-To: <m2mx2jkeb2.fsf@igel.home>
> From: Andreas Schwab <schwab@linux-m68k.org>
> Cc: nicholas.dokos@hp.com, 12074@debbugs.gnu.org
> Date: Sat, 28 Jul 2012 19:04:17 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> From: Nick Dokos <nicholas.dokos@hp.com>
> >> Date: Fri, 27 Jul 2012 23:13:16 -0400
> >> Cc: nicholas.dokos@hp.com
> >>
> >> I just updated emacs from the git repo
> >>
> >> git://repo.or.cz/emacs.git
> >>
> >> git describe says
> >>
> >> v24.0.50-14303-g6aecb14
> >
> > What does this mean in terms of the bzr revisions in the master
> > repository?
>
> $ git fetch origin +refs/notes/commits:refs/notes/commits
> $ git log -1 --pretty=%N v24.0.50-14303-g6aecb14
> dmantipov@yandex.ru-20120727073633-hr2a2i7bm2y35sr0
Thanks. This is:
>bzr revision-info dmantipov@yandex.ru-20120727073633-hr2a2i7bm2y35sr0
109225 dmantipov@yandex.ru-20120727073633-hr2a2i7bm2y35sr0
In the next revision, 109226, Dmitry reverted some of his changes that
caused similar crashes inside GC reported by Chong. So I think this
bug might well be a duplicate of what Chong reported here:
http://lists.gnu.org/archive/html/emacs-devel/2012-07/msg00566.html
next prev parent reply other threads:[~2012-07-28 17:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-28 3:13 bug#12074: emacs crashes on startup Nick Dokos
2012-07-28 7:18 ` Eli Zaretskii
2012-07-28 17:04 ` Andreas Schwab
2012-07-28 17:32 ` Eli Zaretskii [this message]
2012-07-28 18:14 ` Nick Dokos
2012-07-28 19:25 ` Eli Zaretskii
2012-07-28 18:11 ` Nick Dokos
2012-07-28 19:00 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83pq7fhjv4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=12074@debbugs.gnu.org \
--cc=nicholas.dokos@hp.com \
--cc=schwab@linux-m68k.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 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.