From: "Clément Pit--Claudel" <clement.pit@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Bisecting display bugs
Date: Sun, 16 Apr 2017 11:04:13 -0400 [thread overview]
Message-ID: <dad48ebd-b366-b1eb-f359-acb5dbd12fd7@gmail.com> (raw)
In-Reply-To: <4f9332d4-68a8-4179-0ef3-b6aa0bfa04b1@gmail.com>
If there are no further comments, I'll push this soon :)
On 2016-07-23 09:22, Clément Pit--Claudel wrote:
> On 2016-07-23 04:51, Eli Zaretskii wrote:
>>> Cc: Emacs developers <emacs-devel@gnu.org>
>>> From: Clément Pit--Claudel <clement.pit@gmail.com>
>>> Date: Fri, 22 Jul 2016 14:55:36 -0400
>>>
>>> Thanks for your comments! I've attached an updated patch.
>>
>> LGTM, thanks. One comment:
>>
>>> +- You should produce the ‘../reproduce-your-bug.el’ script on your own
>>> + (it should check if the bug exists, and return the right error code
>>> + using ‘(kill-emacs EXIT-CODE)’).
>>
>> Suggest to say explicitly what is "the right error code" (yes, that
>> means repeating what you said just 20 lines above, but the relation is
>> not 100% clear).
>
> Thanks; here's a diff against the previous patch (I've attached the updated patch). I also added a note about full rebuilds.
>
> ---
>
> Some caveats:
>
> - make sure your uncommitted changes are saved somewhere else.
> + make sure your uncommitted changes are saved somewhere else. Also,
> + for bisecting small ranges, a full clean and rebuild might not be
> + needed.
>
> - using ‘(kill-emacs EXIT-CODE)’).
> + using ‘(kill-emacs EXIT-CODE)’: 1 if the bug is present, 0 if it is
> + not, and 125 if it can't tell).
>
> ---
>
next prev parent reply other threads:[~2017-04-16 15:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-10 23:55 Bisecting display bugs Clément Pit--Claudel
2016-07-11 1:40 ` Óscar Fuentes
2016-07-11 14:22 ` Eli Zaretskii
2016-07-11 17:46 ` Óscar Fuentes
2016-07-11 17:54 ` Eli Zaretskii
2016-07-11 18:05 ` Óscar Fuentes
2016-07-22 18:55 ` Clément Pit--Claudel
2016-07-23 8:51 ` Eli Zaretskii
2016-07-23 13:22 ` Clément Pit--Claudel
2017-04-16 15:04 ` Clément Pit--Claudel [this message]
2017-04-16 15:32 ` Noam Postavsky
2017-04-16 20:57 ` Clément Pit-Claudel
2017-04-17 13:13 ` Herring, Davis
2017-04-17 13:43 ` Teemu Likonen
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=dad48ebd-b366-b1eb-f359-acb5dbd12fd7@gmail.com \
--to=clement.pit@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@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 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).