From: Junio C Hamano <gitster@pobox.com>
To: Charvi Mendiratta <charvi077@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Feb 2021, #01; Wed, 3)
Date: Thu, 04 Feb 2021 12:25:27 -0800 [thread overview]
Message-ID: <xmqqft2b60nc.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <CAPSFM5cY6WcH+Mj64pvk_8vQeufj4BT6XOz_qjsCDPk8SvN2oQ@mail.gmail.com> (Charvi Mendiratta's message of "Fri, 5 Feb 2021 00:52:53 +0530")
Charvi Mendiratta <charvi077@gmail.com> writes:
> On Thu, 4 Feb 2021 at 06:00, Junio C Hamano <gitster@pobox.com> wrote:
>
>> * cm/rebase-i (2021-01-29) 9 commits
>> (merged to 'next' on 2021-02-01 at 4f9aa6cec3)
>> + doc/git-rebase: add documentation for fixup [-C|-c] options
>> + rebase -i: teach --autosquash to work with amend!
>> + t3437: test script for fixup [-C|-c] options in interactive rebase
>> + rebase -i: add fixup [-C | -c] command
>> + sequencer: use const variable for commit message comments
>> + sequencer: pass todo_item to do_pick_commit()
>> + rebase -i: comment out squash!/fixup! subjects from squash message
>> + sequencer: factor out code to append squash message
>> + rebase -i: only write fixup-message when it's needed
>>
>> "rebase -i" is getting cleaned up and also enhanced.
>>
>> Will merge to 'master'.
>>
>
> Received reviews and suggestions on this patch series. So, updated
> those changes and have sent the next version of this patch series (v5).
We incrementally fix shortcomings in the series with additional
patches after a topic gets merged to 'next'. It no longer is
appropriate to replace with "the net version".
Thanks.
prev parent reply other threads:[~2021-02-04 20:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 0:27 What's cooking in git.git (Feb 2021, #01; Wed, 3) Junio C Hamano
2021-02-04 19:22 ` Charvi Mendiratta
2021-02-04 20:25 ` Junio C Hamano [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqft2b60nc.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=charvi077@gmail.com \
--cc=git@vger.kernel.org \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.