From: Elijah Newren <newren@gmail.com>
To: Rohit Ashiwal <rohit.ashiwal265@gmail.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
artagnon@gmail.com, Christian Couder <christian.couder@gmail.com>,
Git Mailing List <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: Fri, 29 Mar 2019 16:25:49 -0700 [thread overview]
Message-ID: <CABPp-BETuwt96jeBMMhzT84-=-MqEA3D7uhLb2uxW3fijx7p7Q@mail.gmail.com> (raw)
In-Reply-To: <20190329223228.4924-1-rohit.ashiwal265@gmail.com>
Hi Rohit,
On Fri, Mar 29, 2019 at 3:33 PM Rohit Ashiwal
<rohit.ashiwal265@gmail.com> wrote:
>
> Hiya
>
> This is the v2 of the draft proposal[1]. 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.
Overall this looks pretty good to me, just one question...
> 3. Now that I'm familiar with the code, I'll start picking the pace now. And
> start implementing the meat of the project. The flags. I'll start implementing
> the flags in the following order as [Elijah suggested][12]:
> 1. --ignore-whitespace
> 2. --committer-date-is-author-date
> 3. --ignore-date
> 4. --whitespace=...
> 5. `[Bonus]` --signoff
--signoff is new and surprises me. What's the plan with that one?
next prev parent reply other threads:[~2019-03-29 23:26 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 [this message]
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
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-BETuwt96jeBMMhzT84-=-MqEA3D7uhLb2uxW3fijx7p7Q@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 \
--subject='Re: [GSoC][RFC v2] Improve consistency of sequencer commands' \
/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
Code repositories for project(s) associated with this 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).