From: Pedro Alves <palves@redhat.com>
To: Doug Evans <dje@google.com>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>,
Patrick Palka <patrick@parcs.ath.cx>,
gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] [RFC] Sync readline to version 6.3 patchlevel 8
Date: Thu, 18 Jun 2015 14:08:00 -0000 [thread overview]
Message-ID: <5582D0A4.6010606@redhat.com> (raw)
In-Reply-To: <CADPb22TYrdT1s93qjx3BmuQ5qzyrDJa5ySAmq3ck=47en-tbrw@mail.gmail.com>
On 06/18/2015 02:47 PM, Doug Evans wrote:
> On Thu, Jun 18, 2015 at 5:39 AM, Pedro Alves <palves@redhat.com> wrote:
>> On 05/16/2015 04:51 PM, Doug Evans wrote:
>>> On Sat, May 16, 2015 at 8: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.
>>>
>>> It might. Bleah.
>>>
>>> What's the "git" way to do this (*1) that doesn't involve a lot of
>>> manual effort?
>>> ---
>>> (*1): "this" being extracting out individual local patches later in
>>> time (say a year from now).
>>
>> I guess that would be a git merge of the branch that contains
>> the local patches. We don't allow merge commits in our
>> repo though.
>>
>> I think that easiest next best is to put the unsquashed application
>> of the local patches in a branch (just like users/ppalka/readline-6.3-update),
>> and apply the squashed version to master. For the next update, we can
>> find the initial local patches in the branch.
>
> fwiw, I'm not comfortable with needing to rely on personal branches
> for pretty much anything.
>
> Can we make an official readline merging branch?
> [assuming using a branch is how we want to solve this]
Don't see why not. Is there more to it than picking a name?
Thanks,
Pedro Alves
next prev parent reply other threads:[~2015-06-18 14:08 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
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 [this message]
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=5582D0A4.6010606@redhat.com \
--to=palves@redhat.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=patrick@parcs.ath.cx \
/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