From: "Clément Pit--Claudel" <clement.pit@gmail.com>
To: 23897@debbugs.gnu.org
Subject: bug#23897: 25.1.50; Argument at point not being highlighted in eldoc hints
Date: Thu, 7 Jul 2016 15:36:04 -0400 [thread overview]
Message-ID: <577EAF24.7020403@gmail.com> (raw)
In-Reply-To: <ebc9da29-6644-05d1-65f6-f2fa12d924a5@yandex.ru>
[-- Attachment #1.1: Type: text/plain, Size: 611 bytes --]
On 2016-07-07 13:06, Dmitry Gutov wrote:
> On 07/07/2016 07:57 PM, Kaushal Modi wrote:
>
>> Dumb question. Is the process of bisecting simply building emacs at
>> half-way commits between passing and failing builds till you narrow down
>> to the breaking commit?
>
> Yes. 'git bisect' makes it relatively straightforward, but it can take a lot of time (like an hour, maybe a few), depending on how many commits one has to examine.
>
> You can switch to other work while it builds, though.
If you find a way to automate the test, you can also tell git to find the offending code automatically.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2016-07-07 19:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-05 15:25 bug#23897: 25.1.50; Argument at point not being highlighted in eldoc hints Kaushal Modi
2016-07-07 16:18 ` martin rudalics
2016-07-07 16:28 ` Clément Pit--Claudel
2016-07-07 16:57 ` Kaushal Modi
2016-07-07 17:06 ` Dmitry Gutov
2016-07-07 19:31 ` Kaushal Modi
2016-07-07 19:38 ` Kaushal Modi
2016-07-07 19:44 ` Eli Zaretskii
2016-07-07 20:31 ` Kaushal Modi
2016-07-07 22:19 ` Kaushal Modi
2016-07-08 9:25 ` Eli Zaretskii
2016-07-08 19:39 ` Eli Zaretskii
2016-07-08 19:42 ` Kaushal Modi
2016-07-08 19:49 ` Eli Zaretskii
2016-07-08 20:01 ` Kaushal Modi
2016-07-09 6:40 ` Clément Pit--Claudel
2016-07-07 19:36 ` Clément Pit--Claudel [this message]
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=577EAF24.7020403@gmail.com \
--to=clement.pit@gmail.com \
--cc=23897@debbugs.gnu.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.