From: Elijah Newren <newren@gmail.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: Rohit Ashiwal <rohit.ashiwal265@gmail.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Ramkumar Ramachandra <artagnon@gmail.com>,
git <git@vger.kernel.org>, Stephan Beyer <s-beyer@gmx.net>,
Thomas Gummerer <t.gummerer@gmail.com>,
Alban Gruin <alban.gruin@gmail.com>,
rafa.almas@gmail.com
Subject: Re: [GSoC][RFC v2] Improve consistency of sequencer commands
Date: Sat, 30 Mar 2019 10:12:26 -0700 [thread overview]
Message-ID: <CABPp-BFknrV8ALFTifcZ4-nzqy_yWO=7zdkemzcA2kfrZ+4_9A@mail.gmail.com> (raw)
In-Reply-To: <CAP8UFD3b8wxj=T+HpeFAQNGLghs8fpEvQusP7Wq-BRZb3c50dg@mail.gmail.com>
On Sat, Mar 30, 2019 at 12:16 AM Christian Couder
<christian.couder@gmail.com> wrote:
> > 6. `[Bonus]` If everything goes well and time permits, discuss with the mentor(s)
> > the possibility of deprecating the am backend of rebase. This point is last to
> > work on as it provides no "cosmetic" difference on the user side. Elijah
> > [mentioned][12] the possibility of a "social" problem that might occur which shall
> > be discussed then.
>
> Maybe it would be interesting to see if there is a performance
> difference between the 2 backends.
Yes, it may make sense to repeat
https://public-inbox.org/git/nycvar.QRO.7.76.6.1901312310280.41@tvgsbejvaqbjf.bet/
to verify we're still in a good state, and maybe even try to figure
out why split-index is weird. However, more important is the handling
of empty commits (both start-empty and become-empty) and trying to
bring some consistency there or at least implementing more options for
the interactive backend and figuring out which empty-handling options
should be the default for which sets of flags. It's kind of a mess.
next prev parent reply other threads:[~2019-03-30 17:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-24 10:05 [GSoC] Introduction Rohit Ashiwal
2019-02-24 14:47 ` Johannes Schindelin
2019-02-25 6:50 ` Christian Couder
2019-02-25 11:35 ` Rohit Ashiwal
2019-02-25 20:21 ` Christian Couder
2019-02-25 21:09 ` Eric Sunshine
2019-03-22 15:11 ` [GSoC][RFC] Proposal: Improve consistency of sequencer commands Rohit Ashiwal
2019-03-23 22:17 ` Christian Couder
2019-03-24 1:21 ` Rohit Ashiwal
2019-03-24 1:07 ` Elijah Newren
2019-03-24 1:45 ` Rohit Ashiwal
2019-03-29 22:32 ` [GSoC][RFC v2] " Rohit Ashiwal
2019-03-29 23:25 ` Elijah Newren
2019-03-29 23:34 ` Rohit Ashiwal
2019-03-30 0:38 ` Elijah Newren
2019-03-30 8:48 ` Rohit Ashiwal
2019-03-30 17:13 ` Elijah Newren
2019-03-30 7:16 ` Christian Couder
2019-03-30 17:12 ` Elijah Newren [this message]
2019-04-05 21:31 ` [GSoC][RFC v3] Proposal: " Rohit Ashiwal
2019-04-07 7:15 ` Christian Couder
2019-04-07 12:16 ` Rohit Ashiwal
2019-04-07 23:07 ` Christian Couder
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABPp-BFknrV8ALFTifcZ4-nzqy_yWO=7zdkemzcA2kfrZ+4_9A@mail.gmail.com' \
--to=newren@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=alban.gruin@gmail.com \
--cc=artagnon@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=rafa.almas@gmail.com \
--cc=rohit.ashiwal265@gmail.com \
--cc=s-beyer@gmx.net \
--cc=t.gummerer@gmail.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.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).