git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: js/rebase-am, was Re: What's cooking in git.git (Jan 2019, #04; Mon, 28)
Date: Tue, 29 Jan 2019 15:03:13 +0100 (STD)	[thread overview]
Message-ID: <nycvar.QRO.7.76.6.1901291501320.41@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <xmqq4l9s9zee.fsf@gitster-ct.c.googlers.com>

Hi Junio,

On Mon, 28 Jan 2019, Junio C Hamano wrote:

> * js/rebase-am (2019-01-18) 4 commits
>  - built-in rebase: call `git am` directly
>  - rebase: teach `reset_head()` to optionally skip the worktree
>  - rebase: avoid double reflog entry when switching branches
>  - rebase: move `reset_head()` into a better spot
> 
>  Instead of going through "git-rebase--am" scriptlet to use the "am"
>  backend, the built-in version of "git rebase" learned to drive the
>  "am" backend directly.
> 
>  Waiting for a review response.
>  Looked almost ready.

I responded, clarifying that the code does not change the behavior
relative to the scripted version.

Ciao,
Dscho

  parent reply	other threads:[~2019-01-29 14:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-28 22:43 What's cooking in git.git (Jan 2019, #04; Mon, 28) Junio C Hamano
2019-01-29  7:22 ` Torsten Bögershausen
2019-01-29 12:54 ` pw/rebase-x-sanity-check, was " Johannes Schindelin
2019-01-29 18:11   ` Junio C Hamano
2019-01-29 14:03 ` Johannes Schindelin [this message]
2019-01-29 14:06 ` tt/bisect-in-c, " Johannes Schindelin
2019-01-29 15:39   ` Johannes Schindelin
2019-01-29 14:15 ` en/rebase-merge-on-sequencer, " Johannes Schindelin
2019-01-29 14:21 ` Johannes Schindelin
2019-01-29 14:23 ` ps/stash-in-c, was " Johannes Schindelin
2019-01-29 14:26 ` [PATCH] Fix typos in whats-cooking.txt, " Johannes Schindelin

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=nycvar.QRO.7.76.6.1901291501320.41@tvgsbejvaqbjf.bet \
    --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).