unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Richard Copley <rcopley@gmail.com>
Cc: 11867@debbugs.gnu.org, schwab@linux-m68k.org, lekktu@gmail.com
Subject: bug#11867: 24.1.50; Windows bootstrap crash (converting tit files?)
Date: Sat, 07 Jul 2012 09:31:40 +0300	[thread overview]
Message-ID: <83vci013qr.fsf@gnu.org> (raw)
In-Reply-To: <CAPM58oiBN8v=4ke6u+wY3jE1fVAoy=j9-gewLtwrFSJoHR+ejA@mail.gmail.com>

> Date: Fri, 6 Jul 2012 21:58:24 +0100
> From: Richard Copley <rcopley@gmail.com>
> Cc: Andreas Schwab <schwab@linux-m68k.org>, Eli Zaretskii <eliz@gnu.org>, 
> 	Juanma Barranquero <lekktu@gmail.com>
> 
> >>> (gdb) thread apply all bt full
> 
> OK, thanks. I just bootstrapped 108908 [sic] here (on Windows 7)
> without error. The (XP) machine where I saw the crash is turned off
> now until Monday. I will get the backtrace then, unless you ask me not
> to.

Thanks.  If the latest trunks bootstraps on that XP machine without
problems, there's no need to produce backtrace from an earlier
revisions.

> BTW, is there a recommended way to build a previous revision? I ran
> "bzr revert -r108908" before running Make, which I suppose is good
> enough, but `emacs-bzr-revision' ends up being the latest revision
> that I have pulled.

"bzr revno" shows the revision of your local repository, not of the
tree.  "bzr revert" reverts the tree to the named revision, but does
not remove the info about the next revisions from the repository's
meta-data.

IOW, "bzr revert" is the right way of doing what you ask, it just
doesn't show in "bzr revno".





  reply	other threads:[~2012-07-07  6:31 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-06 15:55 bug#11867: 24.1.50; Windows bootstrap crash (converting tit files?) Richard Copley
2012-07-06 16:02 ` Eli Zaretskii
2012-07-06 16:12   ` Andreas Schwab
2012-07-06 17:33     ` Eli Zaretskii
2012-07-06 17:39       ` Andreas Schwab
2012-07-06 20:58         ` Richard Copley
2012-07-07  6:31           ` Eli Zaretskii [this message]
2012-07-06 16:37 ` Juanma Barranquero
2012-07-06 17:35   ` Eli Zaretskii
2012-07-09  3:56     ` Juanma Barranquero
2012-07-09 16:31       ` Eli Zaretskii
2012-07-09 16:57         ` Juanma Barranquero
2012-07-09 17:09           ` Andreas Schwab
2012-07-09 17:10             ` Juanma Barranquero
2012-07-09 17:14           ` Eli Zaretskii
2012-07-09 17:21             ` Juanma Barranquero
2012-07-09 20:42               ` Eli Zaretskii
2012-07-09 20:54                 ` Juanma Barranquero
2012-07-10  2:43                   ` Eli Zaretskii
2012-07-10 11:38                     ` Juanma Barranquero
2012-07-10 16:11                       ` Eli Zaretskii
2012-07-10 16:36                         ` Juanma Barranquero
2012-07-10 17:35                           ` Eli Zaretskii
2012-07-10 20:20                             ` Juanma Barranquero
2012-07-13  0:19                             ` Juanma Barranquero
2012-07-13  4:57                               ` Eli Zaretskii
2012-07-13  0:13                         ` Juanma Barranquero
2012-07-13  7:57                           ` Eli Zaretskii
2012-07-13  8:30                             ` Juanma Barranquero
2012-07-13 10:19                               ` Eli Zaretskii
2012-07-17 21:35                                 ` Richard Copley
2012-07-17 23:39                                   ` Juanma Barranquero
2013-02-18  2:20                                     ` Glenn Morris
2013-02-18  3:44                                       ` Eli Zaretskii
     [not found]                                     ` <CAPM58og6J2KWsZTAes3E9ZyP=p-oQsW6xwH=5AJMOyTPXU8wYw@mail.gmail.com>
2013-02-18 12:24                                       ` bug#11867: Fwd: " Richard Copley
2012-07-07  9:09   ` Jason Rumney

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=83vci013qr.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=11867@debbugs.gnu.org \
    --cc=lekktu@gmail.com \
    --cc=rcopley@gmail.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 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).