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

[PATCH 7/7] user-manual: use detached head when rewriting history

From
JFJ. Bruce Fields <bfields@citi.umich.edu>
Date
Apr 16, 2007, 04:37 UTC
Message-ID
<9347.04806791178$1176698260@news.gmane.org>
In-Reply-To
<11766982362911-git-send-email->
From: J. Bruce Fields <bfields@citi.umich.edu>

This is slightly simpler if we use a detached head. And it's probably good to have another example that uses this feature.

Signed-off-by: "J. Bruce Fields" <bfields@citi.umich.edu>
---
 Documentation/user-manual.txt |   15 ++++++++-------
 1 files changed, 8 insertions(+), 7 deletions(-)
diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt
index c32aaef..5c62516 100644
--- a/Documentation/user-manual.txt
+++ b/Documentation/user-manual.txt
@@ -504,6 +504,7 @@ $ cat .git/HEAD
 ref: refs/heads/master
 ------------------------------------------------
 
+[[detached-head]]
 Examining an old version without creating a new branch
 ------------------------------------------------------
 
@@ -2055,22 +2056,22 @@ $ git tag bad mywork~5
 
 (Either gitk or git-log may be useful for finding the commit.)
 
-Then check out a new branch at that commit, edit it, and rebase the rest of
-the series on top of it:
+Then check out that commit, edit it, and rebase the rest of the series
+on top of it (note that we could check out the commit on a temporary
+branch, but instead we're using a <<detached-head,detached head>>):
 
 -------------------------------------------------
-$ git checkout -b TMP bad
+$ git checkout bad
 $ # make changes here and update the index
 $ git commit --amend
-$ git rebase --onto TMP bad mywork
+$ git rebase --onto HEAD bad mywork
 -------------------------------------------------
 
-When you're done, you'll be left with mywork checked out, with the top patches
-on mywork reapplied on top of the modified commit you created in TMP.  You can
+When you're done, you'll be left with mywork checked out, with the top
+patches on mywork reapplied on top of your modified commit.  You can
 then clean up with
 
 -------------------------------------------------
-$ git branch -d TMP
 $ git tag -d bad
 -------------------------------------------------
 
-- 
1.5.1.1.98.gedb4f
Previous: J. Bruce Fields
Message 10 of 10 in “Documentation: minor edits of git-lost-found manpage”
  1. 1/7 Documentation: minor edits of git-lost-found manpageJ. Bruce Fields, Apr 16, 2007
  2. 2/7 Documentation: clarify git-checkout -f, minor editingJ. Bruce Fields, Apr 16, 2007
  3. Junio C HamanoApr 16, 2007
  4. J. Bruce FieldsApr 17, 2007
  5. git-commit.txt: better warning about -f optionJ. Bruce Fields, Apr 17, 2007
  6. 3/7 Documentation: clarify track/no-track option.J. Bruce Fields, Apr 16, 2007
  7. 4/7 user-manual: fix discussion of default cloneJ. Bruce Fields, Apr 16, 2007
  8. 5/7 user-manual: detached HEADJ. Bruce Fields, Apr 16, 2007
  9. 6/7 user-manual: start revising "internals" chapterJ. Bruce Fields, Apr 16, 2007
  10. 7/7 user-manual: use detached head when rewriting historyJ. Bruce Fields, Apr 16, 2007

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.