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

Re: [PATCH v2 0/2] checkout: die() on ambiguous tracking branches

From
AMAlexandr Miloslavskiy <alexandr.miloslavskiy@syntevo.com>
Date
Dec 1, 2019, 16:52 UTC
Message-ID
<10e7d07d-9432-1c41-289e-2be86539aa56@syntevo.com>
In-Reply-To
<xmqqwobgyrnf.fsf@gitster-ct.c.googlers.com>
On 01.12.2019 16:47, Junio C Hamano wrote:
Show 9 quoted lines
> When sending an updated series after getting review comments from
> others to your earlier round of the same series, please make sure
> these reviewers are CC'ed, especially those who thought the earlier
> one(s) were not quite right, so that they can say "oh, I changed my
> mind.  This round is good", or "I think it is still wrong in this
> round, because of ...".
> 
> You do not necessarily have to include me on CC: line before the
> list seems to have reached concensus that the patches are good.
OK, thanks for explaining! I'm new and didn't know about that.

For this patch, I already informed reviewers via explicit replies. From the next one, I'll try to remember to also CC them.

Previous: Junio C Hamano
Message 13 of 13 in “checkout: die() on ambiguous tracking branches”
  1. 0/2 checkout: die() on ambiguous tracking branchesAlexandr Miloslavskiy via GitGitGadget, Nov 27, 2019
  2. 1/2 parse_branchname_arg(): extract part as new functionAlexandr Miloslavskiy via GitGitGadget, Nov 27, 2019
  3. 2/2 checkout: die() on ambiguous tracking branchesAlexandr Miloslavskiy via GitGitGadget, Nov 27, 2019
  4. Derrick StoleeNov 27, 2019
  5. Alexandr MiloslavskiyNov 27, 2019
  6. Ævar Arnfjörð BjarmasonNov 27, 2019
  7. Alexandr MiloslavskiyNov 27, 2019
  8. Alexandr MiloslavskiyDec 5, 2019
  9. 0/2 checkout: die() on ambiguous tracking branchesAlexandr Miloslavskiy via GitGitGadget, Nov 27, 2019
  10. 2/2 checkout: die() on ambiguous tracking branchesAlexandr Miloslavskiy via GitGitGadget, Nov 27, 2019
  11. 1/2 parse_branchname_arg(): extract part as new functionAlexandr Miloslavskiy via GitGitGadget, Nov 27, 2019
  12. Junio C HamanoDec 1, 2019
  13. Alexandr MiloslavskiyDec 1, 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.