git/list[1] front-page[2] threads[3] people[4] search[5] about
 

js/rebase-am, was Re: What's cooking in git.git (Jan 2019, #04; Mon, 28)

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Jan 29, 2019, 14:03 UTC
Message-ID
<nycvar.QRO.7.76.6.1901291501320.41@tvgsbejvaqbjf.bet>
In-Reply-To
<xmqq4l9s9zee.fsf@gitster-ct.c.googlers.com>
Hi Junio,
On Mon, 28 Jan 2019, Junio C Hamano wrote:
Show 12 quoted lines
> * 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

Previous: Junio C HamanoNext: Johannes Schindelin
Message 5 of 11 in “What's cooking in git.git (Jan 2019, #04; Mon, 28)”
  1. Junio C HamanoJan 28, 2019
  2. Torsten BögershausenJan 29, 2019
  3. pw/rebase-x-sanity-check, was Re: What's cooking in git.git (Jan 2019, #04; Mon, 28)Johannes Schindelin, Jan 29, 2019
  4. Junio C HamanoJan 29, 2019
  5. js/rebase-am, was Re: What's cooking in git.git (Jan 2019, #04; Mon, 28)Johannes Schindelin, Jan 29, 2019
  6. tt/bisect-in-c, was Re: What's cooking in git.git (Jan 2019, #04; Mon, 28)Johannes Schindelin, Jan 29, 2019
  7. Johannes SchindelinJan 29, 2019
  8. en/rebase-merge-on-sequencer, was Re: What's cooking in git.git (Jan 2019, #04; Mon, 28)Johannes Schindelin, Jan 29, 2019
  9. Johannes SchindelinJan 29, 2019
  10. ps/stash-in-c, was Re: What's cooking in git.git (Jan 2019, #04; Mon, 28)Johannes Schindelin, Jan 29, 2019
  11. Fix typos in whats-cooking.txt, was Re: What's cooking in git.git (Jan 2019, #04; Mon, 28)Johannes Schindelin, Jan 29, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.