From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Sep 2017, #03; Fri, 15)
Date: Fri, 15 Sep 2017 21:14:09 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1.1709152113070.219280@virtualbox> (raw)
In-Reply-To: <xmqq8thgy03t.fsf@gitster.mtv.corp.google.com>
Hi Junio,
On Fri, 15 Sep 2017, Junio C Hamano wrote:
> * js/rebase-i-final (2017-07-27) 10 commits
> - rebase -i: rearrange fixup/squash lines using the rebase--helper
> - t3415: test fixup with wrapped oneline
> - rebase -i: skip unnecessary picks using the rebase--helper
> - rebase -i: check for missing commits in the rebase--helper
> - t3404: relax rebase.missingCommitsCheck tests
> - rebase -i: also expand/collapse the SHA-1s via the rebase--helper
> - rebase -i: do not invent onelines when expanding/collapsing SHA-1s
> - rebase -i: remove useless indentation
> - rebase -i: generate the script via rebase--helper
> - t3415: verify that an empty instructionFormat is handled as before
>
> The final batch to "git rebase -i" updates to move more code from
> the shell script to C.
>
> Expecting a reroll.
Please stop stating that you expect a reroll for rebase-i-extra when you
explicitly stated months ago that you would not take my v6. It gets a bit
annoying.
Thanks,
Dscho
next prev parent reply other threads:[~2017-09-15 19:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-15 5:58 What's cooking in git.git (Sep 2017, #03; Fri, 15) Junio C Hamano
2017-09-15 7:50 ` Lars Schneider
2017-09-19 1:18 ` Junio C Hamano
2017-09-15 19:14 ` Johannes Schindelin [this message]
2017-09-15 20:33 ` Junio C Hamano
2017-09-15 19:23 ` Johannes Schindelin
2017-09-15 20:49 ` Junio C Hamano
2017-09-29 11:39 ` Johannes Schindelin
2017-09-21 21:14 ` Sahil Dua
2017-09-22 0:59 ` Junio C Hamano
2017-09-22 3:39 ` Junio C Hamano
2017-09-24 16:16 ` Sahil Dua
2017-09-25 0:40 ` Junio C Hamano
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=alpine.DEB.2.21.1.1709152113070.219280@virtualbox \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).