From: Wink Saville <wink@saville.com>
To: Jacob Keller <jacob.keller@gmail.com>
Cc: Git List <git@vger.kernel.org>,
Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: Re: Should I try to fix rebase interactive preserve-merges bug
Date: Sun, 25 Mar 2018 13:22:50 -0700 [thread overview]
Message-ID: <CAKk8isp_oFNRNbO0fSJx5GC_QKKiojsL=TxBJu2Z54xp5NCFDA@mail.gmail.com> (raw)
In-Reply-To: <CA+P7+xqqLU-J5hv=yioMxMvp40hz_S9GfimjE7bp1Pj_TP-k3w@mail.gmail.com>
> AFAIK this breakage of preserve-merges is a design flaw which isn't
> really fixable, which is why --recreate-merges is being added.
>
> I believe the plan is to deprecate preserve-merges once
> recreate-merges has landed.
>
> Thanks,
> Jake
Txs for the info, hopefully others will respond.
next prev parent reply other threads:[~2018-03-25 20:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-25 17:32 Should I try to fix rebase interactive preserve-merges bug Wink Saville
2018-03-25 18:07 ` Jacob Keller
2018-03-25 20:22 ` Wink Saville [this message]
2018-03-26 22:00 ` Johannes Schindelin
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='CAKk8isp_oFNRNbO0fSJx5GC_QKKiojsL=TxBJu2Z54xp5NCFDA@mail.gmail.com' \
--to=wink@saville.com \
--cc=git@vger.kernel.org \
--cc=jacob.keller@gmail.com \
--cc=johannes.schindelin@gmx.de \
/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;
as well as URLs for NNTP newsgroup(s).