From: Junio C Hamano <gitster@pobox.com>
To: Pratik Karki <predatoramigo@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Aug 2018, #01; Thu, 2)
Date: Fri, 03 Aug 2018 09:09:35 -0700 [thread overview]
Message-ID: <xmqqftzvzb28.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <CAOZc8M-AqmcbM=Z47SoPpQNaGwFWEbQ=BctXHaYBVeUf9V+j=Q@mail.gmail.com> (Pratik Karki's message of "Fri, 3 Aug 2018 08:45:51 +0545")
Pratik Karki <predatoramigo@gmail.com> writes:
> Hi Junio,
>
> On Fri, Aug 3, 2018 at 4:47 AM Junio C Hamano <gitster@pobox.com> wrote:
>>
>> * pk/rebase-in-c (2018-07-30) 3 commits
>> - builtin/rebase: support running "git rebase <upstream>"
>> - rebase: refactor common shell functions into their own file
>> - rebase: start implementing it as a builtin
>>
>> Rewrite of the "rebase" machinery in C.
>>
>> Will merge to 'next'.
>
> On a recent mail[1], I had suggested stalling this iteration in `pu`
> and wait for another iteration to merge in `next`.
>
> [1]: https://public-inbox.org/git/CAOZc8M_FJmMCEB1MkJrBRpLiFjy8OTEg_MxoNQTh5-brHxR-=A@mail.gmail.com/
Thanks for a prompt response and correction. Very much appreciated.
next prev parent reply other threads:[~2018-08-03 16:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-02 23:02 What's cooking in git.git (Aug 2018, #01; Thu, 2) Junio C Hamano
2018-08-03 0:05 ` Stefan Beller
2018-08-03 16:08 ` Junio C Hamano
2018-08-03 3:00 ` Pratik Karki
2018-08-03 16:09 ` Junio C Hamano [this message]
2018-08-03 18:09 ` brian m. carlson
2018-08-03 18:40 ` Junio C Hamano
2018-08-03 18:45 ` brian m. carlson
2018-08-03 18:51 ` Junio C Hamano
2018-08-03 18:56 ` Junio C Hamano
2018-08-03 19:32 ` Brandon Williams
2018-08-03 20:07 ` Junio C Hamano
2018-08-03 20:43 ` Stefan Beller
2018-08-03 21:45 ` Junio C Hamano
2018-08-05 6:15 ` Junio C Hamano
2018-08-05 0:30 ` pk/rebase-in-c, was " Johannes Schindelin
2018-08-05 6:08 ` Junio C Hamano
2018-08-09 13:24 ` Johannes Schindelin
2018-08-07 10:50 ` Jakub Narebski
2018-08-07 14:36 ` Junio C Hamano
2018-08-07 15:42 ` Jakub Narębski
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=xmqqftzvzb28.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=predatoramigo@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).