From: Christian Couder <email@example.com>
To: Rohit Ashiwal <firstname.lastname@example.org>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Ramkumar Ramachandra <email@example.com>,
git <firstname.lastname@example.org>, Elijah Newren <email@example.com>,
Stephan Beyer <firstname.lastname@example.org>,
Thomas Gummerer <email@example.com>,
Alban Gruin <firstname.lastname@example.org>,
Subject: Re: [GSoC][RFC v2] Improve consistency of sequencer commands
Date: Sat, 30 Mar 2019 08:16:10 +0100 [thread overview]
Message-ID: <CAP8UFD3b8wxj=T+HpeFAQNGLghs8fpEvQusP7Wq-BRZb3c50dg@mail.gmail.com> (raw)
On Fri, Mar 29, 2019 at 11:33 PM Rohit Ashiwal
> This is the v2 of the draft proposal. I've added some details to the proposal,
> it talks more about what to implement instead of how. It is still incomplete.
> I'm currently adding more to the overview section, where I'll document the work
> done by Dscho and Alban. After that I'll find files that will be changed while
> implementing rest of the flags, finally add the basic control and/or data flow
> of the 'how' part.
The plan to improve it looks good to me.
> ### List of Contributions at Git:
> Repo | Status | Title
> [git/git] | Merged in 'next' branch | [Micro]**:** Use helper functions in test script
It would be nice to have a link to the last "What's cooking in
git.git" email from Junio so we can easily see the current status of
your patch/patch series.
> [git-for-windows/git] | Merged and released | [#2077]**:** [FIX] git-archive error, gzip -cn : command not found.
> [git-for-windows/build-extra] | Merged | [#235]**:** installer: Fix version of installer and installed file.
> ## The Project
> ### _Improve consistency of sequencer commands_
> #### Overview
> Stephan Beyer \<email@example.com> tried to introduce git-sequencer as his GSoC
> 2008 [project] which executed a sequence of git instructions to \<HEAD> or
> \<branch> and the sequence was given by a \<file> or through `stdin`. The
> git-sequencer wants to become the common backend for git-am, git-rebase and
> other git commands. Unfortunately, most of the code did not get merged during
> the SoC period but he continued his contributions to the project along with
> Christian Couder \<firstname.lastname@example.org> and then mentor Daniel Barkalow
> The project was continued by Ramkumar Ramachandra \<email@example.com> in
> , converting it to a builtin and extending its domain to
I don't think the sequencer has been converted into a builtin. I am
not sure why Ram wrote that he would do that in his proposal as I
don't think it was really a goal we had.
By the way, you might want to read the sequencer related article in
https://git.github.io/rev_news/2016/10/19/edition-20/ for things that
> The learnings from all those works will serve as a huge headstart this year for
> As of now, there are still some inconsistencies among these commands, e.g.,
> there is no `--skip` flag in `git-cherry-pick` while one exists for
> `git-rebase`. This project aims to remove inconsistencies in how the command
> line options are handled.
> 5. `[Bonus]` As familiarity with the code increases, I might be able to implement
> the feature of rewriting commits in time.
I had to go back to the "Points to work on" section to understand what
this was about. Please describe what this is about in a clearer way.
> 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] 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.
> #### Relevant Work
> Dscho and I had a talk on how a non-am backend should implement `git rebase
> --whitespace=fix`, which he warned may become a large project (as it turns out
> it is a sub-task in one of the [proposed ideas]), we were trying to
> integrate this on git-for-windows first.
> Keeping warning in mind, I discussed this project with Rafael and he suggested
> (with a little bit uncertainty in mind) that I should work on implementing a
> git-diff flag that generates a patch that when applied, will remove whitespace
> errors which I am currently working on.
next prev parent reply other threads:[~2019-03-30 7: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 [this message]
2019-03-30 17:12 ` Elijah Newren
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
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:
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 \
* 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
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).