unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: 13387@debbugs.gnu.org
Subject: bug#13387: emacsclient  -t  suspends  emacs
Date: Sun, 13 Jan 2013 18:56:30 -0500	[thread overview]
Message-ID: <yxqa9sctz69.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <m24nik3clg.fsf@igel.home> (Andreas Schwab's message of "Mon, 14 Jan 2013 00:08:43 +0100")

Andreas Schwab <schwab@linux-m68k.org> writes:

> Dan Nicolaescu <dann@gnu.org> writes:
>
>> The log I shown involved no testing,
>
> Then how do you know whether the commit is good or bad?

Because I've identified the bad commit otherwise.
Then I set 
git bisect good BLAH

where BLAH is the commit just before the bad one.

doing a sequence of
git bisect bad

should converge on the bad commit, not before that, which is what
happened in this case.






  reply	other threads:[~2013-01-13 23:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-08 17:09 bug#13387: emacsclient -t suspends emacs Dan Nicolaescu
2013-01-10  7:04 ` Dan Nicolaescu
2013-01-10  9:39   ` Andreas Schwab
2013-01-10 13:43     ` Dan Nicolaescu
2013-01-11  2:47       ` Paul Eggert
2013-01-13 20:09         ` Dan Nicolaescu
2013-01-13 20:08     ` Dan Nicolaescu
2013-01-13 20:29       ` Andreas Schwab
2013-01-13 21:03         ` Dan Nicolaescu
2013-01-13 23:08           ` Andreas Schwab
2013-01-13 23:56             ` Dan Nicolaescu [this message]
2013-01-14 10:08               ` Andreas Schwab
2013-01-14 18:51                 ` Dan Nicolaescu
2013-01-14 22:43                   ` Andreas Schwab
2013-01-15  4:38                     ` Dan Nicolaescu
2013-01-15  9:12                       ` Andreas Schwab
2013-01-21  3:34                         ` Dan Nicolaescu

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=yxqa9sctz69.fsf@fencepost.gnu.org \
    --to=dann@gnu.org \
    --cc=13387@debbugs.gnu.org \
    --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).