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

Re: [PATCH] fixup! worktree move: new command

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 27, 2017, 17:51 UTC
Message-ID
<xmqqwpdgz8zq.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<alpine.DEB.2.20.1701271150200.3469@virtualbox>
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> always been discussed on the mailing list, I would like to kindly ask you
> to please add this patch to the nd/worktree-move branch for the time being
> (i.e. until Duy responds),

The tip of 'pu' (or anything beyond the tip of 'jch') is not always expected to pass test or even build, and unless I know the OP is leaky or usually slow, a "fixup!" that directly addresses the OP tends to be left for the OP to pick up [*1*] to avoid "ah, you sent a reroll but I already had one squashed locally", which is confusing to both myself and OP (and adds burden to me).

It seems that OP is slower to respond than his usual, so I'll add it to the tip of the topic so that it won't be lost.

[Footnote]
*1* It still is used on my end to leave a mental note to myself that
    the topic is expected/waiting to be rerolled, but that is not
    something you can read in "git log --first-parent master..pu".
Previous: Johannes SchindelinNext: Johannes Schindelin
Message 3 of 4 in “fixup! worktree move: new command”
  1. fixup! worktree move: new commandJohannes Schindelin, Jan 25, 2017
  2. Johannes SchindelinJan 27, 2017
  3. Junio C HamanoJan 27, 2017
  4. Johannes SchindelinJan 30, 2017

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.