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

Re: [PATCH 1/2] rebase -i: demonstrate incorrect behavior of post-rewrite

From
Roberto Tyley <roberto.tyley@gmail.com>
Date
Jun 1, 2015, 22:17 UTC
Message-ID
<CAFY1edb75T91EMM6v4wWz09HZruTsioVmXxmZYjnGpK+_qshow@mail.gmail.com>
In-Reply-To
<xmqqd21sfvsm.fsf@gitster.dls.corp.google.com>
On 22 May 2015 at 16:59, Junio C Hamano <gitster@pobox.com> wrote:
> Roberto, isn't your threading of multi-patch series busted?
>
> Why is 1/2 a follow-up to 2/2?  Do you have a time-machine ;-)?
Oh, embarrassing, I better destroy the time-machine:
https://github.com/rtyley/submitgit/pull/5

This was due to me not realising that the GitHub API returns commit lists for PRs in reverse-chronological order... thanks for pointing that out!

Previous: Junio C HamanoNext: Junio C Hamano
Message 6 of 7 in “rebase -i: fix post-rewrite hook with failed exec command”
  1. 2/2 rebase -i: fix post-rewrite hook with failed exec commandMatthieu Moy, May 22, 2015
  2. 1/2 rebase -i: demonstrate incorrect behavior of post-rewriteMatthieu Moy, May 22, 2015
  3. Junio C HamanoMay 22, 2015
  4. Matthieu MoyMay 22, 2015
  5. Junio C HamanoMay 22, 2015
  6. Roberto TyleyJun 1, 2015
  7. Junio C HamanoMay 22, 2015

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.