From: Christian Couder <email@example.com> To: Rohit Ashiwal <firstname.lastname@example.org> Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>, Alban Gruin <email@example.com>, Ramkumar Ramachandra <firstname.lastname@example.org>, git <email@example.com>, Elijah Newren <firstname.lastname@example.org>, email@example.com, Stephan Beyer <firstname.lastname@example.org>, Thomas Gummerer <email@example.com> Subject: Re: [GSoC][RFC v3] Proposal: Improve consistency of sequencer commands Date: Mon, 8 Apr 2019 01:07:53 +0200 [thread overview] Message-ID: <CAP8UFD05JDsh2v15GgP+LpPKVAK-Dg4k0aicScY5p=za4gsTGw@mail.gmail.com> (raw) In-Reply-To: <firstname.lastname@example.org> Hi Rohit, On Sun, Apr 7, 2019 at 2:17 PM Rohit Ashiwal <email@example.com> wrote: > > On Sun, 7 Apr 2019 09:15:30 +0200 Christian Couder <firstname.lastname@example.org> wrote: > > > As we are close to the deadline (April 9th) for proposal submissions, > > I think it's a good idea to already upload your draft proposal on the > > GSoC site. I think you will be able to upload newer versions until the > > deadline, but uploading soon avoid possible last minute issues and > > mistakes. > > Sure, I'll upload my proposal as soon as possible. Great! > > It looks like you copy pasted the Git Rev News article without > > updating the content. The improvement has been released a long time > > ago. > > The intention was to document how the project started and *major* milestones or > turning points of the project. Here they are. Yeah, the intention is good, though it would be nice if the details were a bit more polished. > > Maybe s/rebases/rebase/ > > Yes, :P > > > It seems to me that there has been more recent work than this and also > > perhaps interesting suggestions and discussions about possible > > sequencer related improvements on the mailing list. > > Again the idea was to document earlier stages of project, "recent" discussions > have been on the optimizations which are not exactly relevant. I think there were ideas (from Elijah) about using the sequencer in the regular (non interactive) rebase too. > Should I write more about recent developments? I think Alban's GSoC project was relevant too. So yeah, if you have time after uploading your proposal to the GSoC web site, it would be nice if you can update it with a bit more information about what happened recently. Thanks, Christian.
prev parent reply other threads:[~2019-04-07 23:08 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 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 [this message]
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='CAP8UFD05JDsh2v15GgP+LpPKVAK-Dg4k0aicScY5p=za4gsTGw@mail.gmail.com' \ --email@example.com \ --cc=Johannes.Schindelin@gmx.de \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [GSoC][RFC v3] Proposal: 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).