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

[PATCH 07/11] Improve section "Manipulating branches"

From
Thomas Ackermann <th.acker@arcor.de>
Date
Aug 27, 2013, 18:02 UTC
Message-ID
<1088240617.34545.1377626528726.JavaMail.ngmail@webmail19.arcor-online.net>
In-Reply-To
<1403569571.34349.1377625974290.JavaMail.ngmail@webmail19.arcor-online.net>

Add some missing punctuation. Simplify description of "git branch -d/-D".

Signed-off-by: Thomas Ackermann <th.acker@arcor.de>
---
 Documentation/user-manual.txt | 20 ++++++++------------
 1 file changed, 8 insertions(+), 12 deletions(-)
diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt
index 98d2804..c20e8df 100644
--- a/Documentation/user-manual.txt
+++ b/Documentation/user-manual.txt
@@ -268,27 +268,23 @@ Creating, deleting, and modifying branches is quick and easy; here's
 a summary of the commands:
 
 `git branch`::
-	list all branches
+	list all branches.
 `git branch <branch>`::
 	create a new branch named `<branch>`, referencing the same
-	point in history as the current branch
+	point in history as the current branch.
 `git branch <branch> <start-point>`::
 	create a new branch named `<branch>`, referencing
 	`<start-point>`, which may be specified any way you like,
-	including using a branch name or a tag name
+	including using a branch name or a tag name.
 `git branch -d <branch>`::
-	delete the branch `<branch>`; if the branch you are deleting
-	points to a commit which is not reachable from the current
-	branch, this command will fail with a warning.
+	delete the branch `<branch>`; if the branch is not fully
+	merged in its upstream branch or contained in the current branch, 
+	this command will fail with a warning.
 `git branch -D <branch>`::
-	even if the branch points to a commit not reachable
-	from the current branch, you may know that that commit
-	is still reachable from some other branch or tag.  In that
-	case it is safe to use this command to force Git to delete
-	the branch.
+	delete the branch `<branch>` irrespective of its merged status.
 `git checkout <branch>`::
 	make the current branch `<branch>`, updating the working
-	directory to reflect the version referenced by `<branch>`
+	directory to reflect the version referenced by `<branch>`.
 `git checkout -b <new> <start-point>`::
 	create a new branch `<new>` referencing `<start-point>`, and
 	check it out.
-- 
1.8.3.msysgit.0


---
Thomas
Previous: Junio C HamanoNext: Junio C Hamano
Message 20 of 28 in “Modernize user-manual”
  1. 0/11 Modernize user-manualThomas Ackermann, Aug 27, 2013
  2. 01/11 Call it "Git User Manual" and remove reference to very old Git versionThomas Ackermann, Aug 27, 2013
  3. Junio C HamanoAug 27, 2013
  4. Lars Gullik BjønnesAug 27, 2013
  5. Junio C HamanoAug 29, 2013
  6. 02/11 Use current "detached HEAD" messageThomas Ackermann, Aug 27, 2013
  7. Junio C HamanoAug 29, 2013
  8. 03/11 Use current output for "git repack"Thomas Ackermann, Aug 27, 2013
  9. Junio C HamanoAug 29, 2013
  10. 04/11 Use "git merge" instead of "git pull ."Thomas Ackermann, Aug 27, 2013
  11. Junio C HamanoAug 27, 2013
  12. Jonathan NiederAug 27, 2013
  13. Junio C HamanoAug 27, 2013
  14. 05/11 Fix some typos and improve wordingThomas Ackermann, Aug 27, 2013
  15. Junio C HamanoAug 27, 2013
  16. Junio C HamanoAug 29, 2013
  17. 06/11 Simplify "How to make a commit"Thomas Ackermann, Aug 27, 2013
  18. Junio C HamanoAug 27, 2013
  19. Junio C HamanoAug 29, 2013
  20. 07/11 Improve section "Manipulating branches"Thomas Ackermann, Aug 27, 2013
  21. Junio C HamanoAug 27, 2013
  22. 08/11 Improve section "Merging multiple trees"Thomas Ackermann, Aug 27, 2013
  23. Junio C HamanoAug 27, 2013
  24. 09/11 Remove unnecessary historical note from "Object storage format"Thomas Ackermann, Aug 27, 2013
  25. Junio C HamanoAug 27, 2013
  26. 10/11 Remove irrelevant reference from "Tying it all together"Thomas Ackermann, Aug 27, 2013
  27. 11/11 "git prune" is safeThomas Ackermann, Aug 27, 2013
  28. Junio C HamanoAug 27, 2013

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.