From: jidanni@jidanni.org
To: git@vger.kernel.org
Cc: gitster@pobox.com
Subject: [PATCH] Documentation/gittutorial.txt: clarify git branch -d
Date: Tue, 6 Jan 2009 10:40:55 +0800 [thread overview]
Message-ID: <1231209655-13050-1-git-send-email-jidanni@jidanni.org> (raw)
Signed-off-by: jidanni <jidanni@jidanni.org>
---
Documentation/gittutorial.txt | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/gittutorial.txt b/Documentation/gittutorial.txt
index 7892244..4581a5a 100644
--- a/Documentation/gittutorial.txt
+++ b/Documentation/gittutorial.txt
@@ -260,11 +260,11 @@ At this point you could delete the experimental branch with
$ git branch -d experimental
------------------------------------------------
-This command ensures that the changes in the experimental branch are
-already in the current branch.
+This command makes sure that the changes in the experimental branch are
+already in the current branch before deleting.
If you develop on a branch crazy-idea, then regret it, you can always
-delete the branch with
+force deletion of the branch with
-------------------------------------
$ git branch -D crazy-idea
--
1.6.0.6
reply other threads:[~2009-01-06 2:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1231209655-13050-1-git-send-email-jidanni@jidanni.org \
--to=jidanni@jidanni.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).