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

[PATCH 3/5] user-manual: mention git-gui

From
JFJ. Bruce Fields <bfields@citi.umich.edu>
Date
Aug 6, 2007, 04:34 UTC
Message-ID
<37994.1480620348$1186374889@news.gmane.org>
In-Reply-To
<11863748422754-git-send-email->
From: J. Bruce Fields <bfields@pig.linuxdev.us.dell.com>

The git gui project seems to be still in early stages, but at a point where it's worth mentioning as an alternative way of creating commits.

One feature of interest is the ability to manipulate individual diff hunks. However, people have found that feature not to be easily discoverable from the user-interface. Pending some ui improvements, a parenthetical hint here may help.

(Thanks to Steffen Prohask and Junio Hamano for suggesting the language.)

Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
---
 Documentation/user-manual.txt |   11 +++++++++--
 1 files changed, 9 insertions(+), 2 deletions(-)
diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt
index 9efe85c..f89952a 100644
--- a/Documentation/user-manual.txt
+++ b/Documentation/user-manual.txt
@@ -1079,6 +1079,11 @@ $ git diff HEAD	    # difference between HEAD and working tree; what
 $ git status	    # a brief per-file summary of the above.
 -------------------------------------------------
 
+You can also use gitlink:git-gui[1] to create commits, view changes in
+the index and the working tree files, and individually select diff hunks
+for inclusion in the index (by right-clicking on the diff hunk and
+choosing "Stage Hunk For Commit").
+
 [[creating-good-commit-messages]]
 Creating good commit messages
 -----------------------------
@@ -2506,8 +2511,10 @@ $ gitk origin..mywork &
 
 And browse through the list of patches in the mywork branch using gitk,
 applying them (possibly in a different order) to mywork-new using
-cherry-pick, and possibly modifying them as you go using commit
---amend.
+cherry-pick, and possibly modifying them as you go using commit --amend.
+The git-gui[1] command may also help as it allows you to individually
+select diff hunks for inclusion in the index (by right-clicking on the
+diff hunk and choosing "Stage Hunk for Commit").
 
 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.GIT
Previous: J. Bruce FieldsNext: J. Bruce Fields
Message 3 of 5 in “user-manual: update for new default --track behavior”
  1. 1/5 user-manual: update for new default --track behaviorJ. Bruce Fields, Aug 6, 2007
  2. 2/5 user-manual: mention git stashJ. Bruce Fields, Aug 6, 2007
  3. 3/5 user-manual: mention git-guiJ. Bruce Fields, Aug 6, 2007
  4. 4/5 documentation: use the word "index" in the git-add manual pageJ. Bruce Fields, Aug 6, 2007
  5. 5/5 documentation: use the word "index" in the git-commit man pageJ. Bruce Fields, Aug 6, 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.