From: Patrick Palka <patrick@parcs.ath.cx>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Doug Evans <dje@google.com>, gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] [RFC] Sync readline to version 6.3 patchlevel 8
Date: Sat, 16 May 2015 15:50:00 -0000 [thread overview]
Message-ID: <CA+C-WL-A46fNMKtMKG5XfoHjESfbh+_ss0BncdB+GK9hEFsRvA@mail.gmail.com> (raw)
In-Reply-To: <20150516152514.GA12510@host1.jankratochvil.net>
On Sat, May 16, 2015 at 11:25 AM, Jan Kratochvil
<jan.kratochvil@redhat.com> wrote:
> On Sat, 16 May 2015 17:23:23 +0200, Doug Evans wrote:
>> Another thought is that IWBN if the reapplication of local patches was
>> a separate commit.
>
> IIUC this would break git bisect.
Unless the local patch fixes a major issue (or perhaps a build error),
I don't think separately reapplying local patches would "break" git
bisect but it would possibly introduce temporary readline-related
testsuite regressions which are not relevant unless you're already
bisecting a readline-related issue. I haven't used git bisect so I
may be wrong... But if that's the case then IMO it's worth the
"breakage".
next prev parent reply other threads:[~2015-05-16 15:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 0:12 Patrick Palka
2015-05-14 1:40 ` Patrick Palka
2015-05-18 11:38 ` Patrick Palka
2015-05-18 11:41 ` Patrick Palka
2015-06-18 10:41 ` Pedro Alves
2015-05-14 9:29 ` Pedro Alves
2015-05-16 1:00 ` Doug Evans
2015-05-16 14:59 ` Patrick Palka
2015-05-16 15:23 ` Doug Evans
2015-05-16 15:25 ` Jan Kratochvil
2015-05-16 15:50 ` Patrick Palka [this message]
2015-05-16 16:06 ` Jan Kratochvil
2015-05-16 15:51 ` Doug Evans
2015-06-18 10:39 ` Pedro Alves
2015-06-18 13:47 ` Doug Evans
2015-06-18 14:08 ` Pedro Alves
2015-06-18 14:20 ` Doug Evans
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=CA+C-WL-A46fNMKtMKG5XfoHjESfbh+_ss0BncdB+GK9hEFsRvA@mail.gmail.com \
--to=patrick@parcs.ath.cx \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox