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

[PATCH v2 3/4] builtin/commit: suggest update-ref for pseudoref removal

From
Han-Wen Nienhuys via GitGitGadget <gitgitgadget@gmail.com>
Date
Aug 19, 2020, 15:15 UTC
Message-ID
<2681638651debf267bbe7e45e41decca5852808b.1597850128.git.gitgitgadget@gmail.com>
In-Reply-To
<pull.706.v2.git.1597850128.gitgitgadget@gmail.com>
From: Han-Wen Nienhuys <hanwen@google.com>

When pseudorefs move to a different ref storage mechanism, pseudorefs no longer can be removed with 'rm'. Instead, suggest a "update-ref -d" command, which will work regardless of ref storage backend.

Signed-off-by: Han-Wen Nienhuys <hanwen@google.com>
---
 builtin/commit.c | 30 +++++++++++++++---------------
 1 file changed, 15 insertions(+), 15 deletions(-)
diff --git a/builtin/commit.c b/builtin/commit.c
index 69ac78d5e5..a4e5e395ba 100644
--- a/builtin/commit.c
+++ b/builtin/commit.c
@@ -844,24 +844,24 @@ static int prepare_to_commit(const char *index_file, const char *prefix,
 		struct ident_split ci, ai;
 
 		if (whence != FROM_COMMIT) {
+			const char *pseudoref = (whence == FROM_MERGE) ?
+							      "MERGE_HEAD" :
+							      "CHERRY_PICK_HEAD";
+			const char *what = (whence == FROM_MERGE) ?
+							 "merge" :
+							 "cherry-pick";
+
 			if (cleanup_mode == COMMIT_MSG_CLEANUP_SCISSORS &&
 				!merge_contains_scissors)
 				wt_status_add_cut_line(s->fp);
-			status_printf_ln(s, GIT_COLOR_NORMAL,
-			    whence == FROM_MERGE
-				? _("\n"
-					"It looks like you may be committing a merge.\n"
-					"If this is not correct, please remove the file\n"
-					"	%s\n"
-					"and try again.\n")
-				: _("\n"
-					"It looks like you may be committing a cherry-pick.\n"
-					"If this is not correct, please remove the file\n"
-					"	%s\n"
-					"and try again.\n"),
-				whence == FROM_MERGE ?
-					git_path_merge_head(the_repository) :
-					git_path_cherry_pick_head(the_repository));
+			status_printf_ln(
+				s, GIT_COLOR_NORMAL,
+				_("\n"
+				  "It looks like you may be committing a %s.\n"
+				  "If this is not correct, please remove %s with\n"
+				  "	git update-ref -d %s\n"
+				  "and try again.\n"),
+				what, pseudoref, pseudoref);
 		}
 
 		fprintf(s->fp, "\n");
-- 
gitgitgadget
Previous: Han-Wen Nienhuys via GitGitGadgetNext: Junio C Hamano
Message 14 of 23 in “Use refs API for handling sundry pseudorefs”
  1. 0/3 Use refs API for handling sundry pseudorefsHan-Wen Nienhuys via GitGitGadget, Aug 18, 2020
  2. 1/3 Make refs_ref_exists publicHan-Wen Nienhuys via GitGitGadget, Aug 18, 2020
  3. Junio C HamanoAug 18, 2020
  4. 2/3 Treat CHERRY_PICK_HEAD as a pseudo refHan-Wen Nienhuys via GitGitGadget, Aug 18, 2020
  5. Junio C HamanoAug 18, 2020
  6. Han-Wen NienhuysAug 19, 2020
  7. Junio C HamanoAug 19, 2020
  8. 3/3 Treat REVERT_HEAD as a pseudo refHan-Wen Nienhuys via GitGitGadget, Aug 18, 2020
  9. Junio C HamanoAug 18, 2020
  10. Junio C HamanoAug 18, 2020
  11. 0/4 Use refs API for handling sundry pseudorefsHan-Wen Nienhuys via GitGitGadget, Aug 19, 2020
  12. 1/4 refs: make refs_ref_exists publicHan-Wen Nienhuys via GitGitGadget, Aug 19, 2020
  13. 2/4 sequencer: treat CHERRY_PICK_HEAD as a pseudo refHan-Wen Nienhuys via GitGitGadget, Aug 19, 2020
  14. 3/4 builtin/commit: suggest update-ref for pseudoref removalHan-Wen Nienhuys via GitGitGadget, Aug 19, 2020
  15. Junio C HamanoAug 19, 2020
  16. Han-Wen NienhuysAug 21, 2020
  17. 4/4 sequencer: treat REVERT_HEAD as a pseudo refHan-Wen Nienhuys via GitGitGadget, Aug 19, 2020
  18. 0/4 Use refs API for handling sundry pseudorefsHan-Wen Nienhuys via GitGitGadget, Aug 21, 2020
  19. 4/4 sequencer: treat REVERT_HEAD as a pseudo refHan-Wen Nienhuys via GitGitGadget, Aug 21, 2020
  20. 2/4 sequencer: treat CHERRY_PICK_HEAD as a pseudo refHan-Wen Nienhuys via GitGitGadget, Aug 21, 2020
  21. 1/4 refs: make refs_ref_exists publicHan-Wen Nienhuys via GitGitGadget, Aug 21, 2020
  22. 3/4 builtin/commit: suggest update-ref for pseudoref removalHan-Wen Nienhuys via GitGitGadget, Aug 21, 2020
  23. Junio C HamanoAug 21, 2020

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.