From: Eli Zaretskii <eliz@gnu.org>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: ofv@wanadoo.es, hanche@math.ntnu.no, emacs-devel@gnu.org
Subject: Re: Emacs seems awfully unstable on OS X lately
Date: Sat, 15 Sep 2012 12:58:46 +0300 [thread overview]
Message-ID: <83d31ntxnt.fsf@gnu.org> (raw)
In-Reply-To: <874nmzr5i5.fsf@uwakimon.sk.tsukuba.ac.jp>
> From: "Stephen J. Turnbull" <stephen@xemacs.org>
> Date: Sat, 15 Sep 2012 18:37:38 +0900
> Cc: Harald Hanche-Olsen <hanche@math.ntnu.no>, emacs-devel@gnu.org
>
> bzr branch --revision=109469 trunk no-109470
> cd no-109470
> bzr merge --revision 109471..last:0 ../trunk
>
> should do the trick.
Why is the second command necessary? Are you assuming that the bug
was introduced after 109470?
My line of thought was: it's quite easy to establish whether the bug
is present in 109471, with 109470 reverse cherry-picked. If it is
present, bisect the trunk where 109470 is removed; if it is not
present, bisect the branch created by the first command above.
Wouldn't that work, too?
next prev parent reply other threads:[~2012-09-15 9:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-14 7:25 Emacs seems awfully unstable on OS X lately Harald Hanche-Olsen
2012-09-14 8:37 ` Ivan Andrus
2012-09-14 15:24 ` Harald Hanche-Olsen
2012-09-14 15:40 ` Óscar Fuentes
2012-09-14 15:59 ` Harald Hanche-Olsen
2012-09-14 19:37 ` Harald Hanche-Olsen
2012-09-14 19:46 ` Harald Hanche-Olsen
2012-09-14 21:15 ` Harald Hanche-Olsen
2012-09-14 21:36 ` Harald Hanche-Olsen
2012-09-14 23:00 ` Óscar Fuentes
2012-09-15 6:54 ` Andreas Schwab
2012-09-15 7:16 ` Eli Zaretskii
2012-09-15 9:37 ` Stephen J. Turnbull
2012-09-15 9:58 ` Eli Zaretskii [this message]
2012-09-15 13:46 ` Stephen J. Turnbull
2012-09-15 14:21 ` Eli Zaretskii
2012-09-15 15:00 ` Stephen J. Turnbull
2012-09-15 9:57 ` Harald Hanche-Olsen
2012-09-16 0:47 ` Harald Hanche-Olsen
2012-09-16 8:04 ` Jan Djärv
2012-09-16 13:15 ` Harald Hanche-Olsen
2012-09-16 15:21 ` Jan Djärv
2012-09-16 15:47 ` Harald Hanche-Olsen
2012-09-16 18:27 ` Jan Djärv
2012-09-17 7:14 ` Harald Hanche-Olsen
2012-09-24 9:54 ` Harald Hanche-Olsen
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=83d31ntxnt.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=hanche@math.ntnu.no \
--cc=ofv@wanadoo.es \
--cc=stephen@xemacs.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).