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

[PATCH 0/2] checkout: don't revert file on ambiguous tracking branches

From
AGAlexandr Miloslavskiy via GitGitGadget <gitgitgadget@gmail.com>
Date
Dec 30, 2019, 18:38 UTC
Message-ID
<pull.504.git.1577731093.gitgitgadget@gmail.com>

This is an improved version of [1]; I tried to clarify the commit message. CC'ing authors of previous commits mentioned in my commit message.

[1] https://public-inbox.org/git/pull.477.git.1574848137.gitgitgadget@gmail.com/T/#u
Alexandr Miloslavskiy (2):
  parse_branchname_arg(): extract part as new function
  checkout: don't revert file on ambiguous tracking branches
 builtin/checkout.c       | 71 ++++++++++++++++++++++------------------
 t/t2024-checkout-dwim.sh | 28 ++++++++++++++--
 2 files changed, 65 insertions(+), 34 deletions(-)
base-commit: 0a76bd7381ec0dbb7c43776eb6d1ac906bca29e6
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-504%2FSyntevoAlex%2F%230207(git)_2c_prevent_ambiguous_checkout-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-504/SyntevoAlex/#0207(git)_2c_prevent_ambiguous_checkout-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/504
-- 
gitgitgadget
Next: Alexandr Miloslavskiy via GitGitGadget
Message 1 of 3 in “checkout: don't revert file on ambiguous tracking branches”
  1. 0/2 checkout: don't revert file on ambiguous tracking branchesAlexandr Miloslavskiy via GitGitGadget, Dec 30, 2019
  2. 1/2 parse_branchname_arg(): extract part as new functionAlexandr Miloslavskiy via GitGitGadget, Dec 30, 2019
  3. 2/2 checkout: don't revert file on ambiguous tracking branchesAlexandr Miloslavskiy via GitGitGadget, Dec 30, 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.