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

[PATCH v2] user-manual: mention git gui citool (commit, amend)

From
Steffen Prohaska <prohaska@zib.de>
Date
Aug 5, 2007, 12:59 UTC
Message-ID
<1186318785677-git-send-email-prohaska@zib.de>
In-Reply-To
<20070803125634.GB28323@fieldses.org>

git gui is especially useful because it allows to select diff hunks. Now it is briefly mentioned in the user-manual.

Signed-off-by: Steffen Prohaska <prohaska@zib.de>
---
 Documentation/user-manual.txt |   15 +++++++++++++++
 1 files changed, 15 insertions(+), 0 deletions(-)
diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt
index 0071cd0..6865d21 100644
--- a/Documentation/user-manual.txt
+++ b/Documentation/user-manual.txt
@@ -1079,6 +1079,17 @@ $ git diff HEAD	    # difference between HEAD and working tree; what
 $ git status	    # a brief per-file summary of the above.
 -------------------------------------------------
 
+Another approach for creating commits is git gui:
+
+-------------------------------------------------
+$ git gui citool
+-------------------------------------------------
+
+starts the commit tool, which lets you add files (use menu
+'Commit > Stage to Commit') or individually diff hunks (use
+'Stage Hunk For Commit' in the context menu of the diff view)
+to the index.
+
 [[creating-good-commit-messages]]
 Creating good commit messages
 -----------------------------
@@ -2482,6 +2493,10 @@ applying them (possibly in a different order) to mywork-new using
 cherry-pick, and possibly modifying them as you go using commit
 --amend.
 
+git gui is especially useful to rework commits as it lets you
+selectively add single diff hunks to the index (use
+'Stage Hunk For Commit' in the context menu of the diff view).
+
 Another technique is to use git-format-patch to create a series of
 patches, then reset the state to before the patches:
 
-- 
1.5.3.rc3.151.g8d6306
Previous: J. Bruce FieldsNext: Johannes Schindelin
Message 8 of 34 in “user-manual: mention git gui citool (commit, amend)”
  1. user-manual: mention git gui citool (commit, amend)Steffen Prohaska, Jul 30, 2007
  2. Shawn O. PearceJul 31, 2007
  3. J. Bruce FieldsAug 2, 2007
  4. Steffen ProhaskaAug 2, 2007
  5. J. Bruce FieldsAug 2, 2007
  6. Steffen ProhaskaAug 3, 2007
  7. J. Bruce FieldsAug 3, 2007
  8. user-manual: mention git gui citool (commit, amend)Steffen Prohaska, Aug 5, 2007
  9. Johannes SchindelinAug 5, 2007
  10. Steffen ProhaskaAug 5, 2007
  11. Johannes SchindelinAug 5, 2007
  12. David KastrupAug 5, 2007
  13. Steffen ProhaskaAug 5, 2007
  14. Johannes SchindelinAug 6, 2007
  15. Steffen ProhaskaAug 6, 2007
  16. Steven GrimmAug 6, 2007
  17. Johannes SchindelinAug 6, 2007
  18. J. Bruce FieldsAug 5, 2007
  19. J. Bruce FieldsAug 5, 2007
  20. Johannes SchindelinAug 6, 2007
  21. J. Bruce FieldsAug 6, 2007
  22. Robin RosenbergAug 6, 2007
  23. J. Bruce FieldsAug 6, 2007
  24. Shawn O. PearceAug 3, 2007
  25. J. Bruce FieldsAug 3, 2007
  26. Shawn O. PearceAug 4, 2007
  27. Steffen ProhaskaAug 5, 2007
  28. Junio C HamanoAug 3, 2007
  29. Shawn O. PearceAug 3, 2007
  30. J. Bruce FieldsAug 3, 2007
  31. Shawn O. PearceAug 4, 2007
  32. David KastrupAug 4, 2007
  33. J. Bruce FieldsAug 4, 2007
  34. Steffen ProhaskaAug 5, 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.