From: Jan Hudec <bulb@ucw.cz>
To: osv@javad.com
Cc: Jakub Narebski <jnareb@gmail.com>,
Steffen Prohaska <prohaska@zib.de>,
git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: [PATCH] Improve description of git-branch -d and -D in man page.
Date: Sat, 17 Nov 2007 20:51:44 +0100 [thread overview]
Message-ID: <20071117195144.GF5198@efreet.light.src> (raw)
In-Reply-To: <20071117191256.GD5198@efreet.light.src>
Some users expect that deleting a remote-tracking branch would prevent
fetch from creating it again, so be explcit about that it's not the case.
Also be a little more explicit about what fully merged means.
Signed-off-by: Jan Hudec <bulb@ucw.cz>
---
On Sat, Nov 17, 2007 at 20:12:56 +0100, Jan Hudec wrote:
> On Tue, Nov 13, 2007 at 20:58:20 +0300, osv@javad.com wrote:
> > <quote Documentation/git-branch.txt>
> > Delete unneeded branch::
> > +
> > ------------
> > $ git clone git://git.kernel.org/.../git.git my.git
> > $ cd my.git
> > $ git branch -d -r origin/todo origin/html origin/man <1>
> > $ git branch -D test <2>
> > ------------
> > +
> > <1> Delete remote-tracking branches "todo", "html", "man"
> > </quote>
> >
> > That's *exactly* what I did! And it *doesn't work*! Well, it does delete
> > the branches, but they are automagically re-created on the next fetch,
> > so "deleting" them this way is useless.
>
> Of course it *does* work. It *deletes* the branches. There is not a single
> word about stopping fetch getting them!
>
> Obviously given that the example is slightly contrived, it should really
> be mentioned that it does not affect fetch at all.
Would this make the description obvious enough?
--
Jan 'Bulb' Hudec <bulb@ucw.cz>
Documentation/git-branch.txt | 21 ++++++++++++++-------
1 files changed, 14 insertions(+), 7 deletions(-)
diff --git a/Documentation/git-branch.txt b/Documentation/git-branch.txt
index 5ce905d..f87b696 100644
--- a/Documentation/git-branch.txt
+++ b/Documentation/git-branch.txt
@@ -45,17 +45,22 @@ to happen.
With a `-d` or `-D` option, `<branchname>` will be deleted. You may
specify more than one branch for deletion. If the branch currently
-has a reflog then the reflog will also be deleted. Use -r together with -d
-to delete remote-tracking branches.
+has a reflog then the reflog will also be deleted.
+
+Use -r together with -d to delete remote-tracking branches. Note, that it
+only makes sense to delete remote-tracking branches if they no longer exist
+in remote repository or if gitlink:git-fetch[1] was configured not to fetch
+them again. See also 'prune' subcommand of gitlink:git-remote[1] for way to
+clean up all obsolete remote-tracking branches.
OPTIONS
-------
-d::
- Delete a branch. The branch must be fully merged.
+ Delete a branch. The branch must be fully merged in HEAD.
-D::
- Delete a branch irrespective of its index status.
+ Delete a branch irrespective of its merged status.
-l::
Create the branch's reflog. This activates recording of
@@ -153,9 +158,11 @@ $ git branch -d -r origin/todo origin/html origin/man <1>
$ git branch -D test <2>
------------
+
-<1> Delete remote-tracking branches "todo", "html", "man"
-<2> Delete "test" branch even if the "master" branch does not have all
-commits from test branch.
+<1> Delete remote-tracking branches "todo", "html", "man". Next 'fetch' or
+'pull' will create them again unless you configure them not to. See
+gitlink:git-fetch[1].
+<2> Delete "test" branch even if the "master" branch (or whichever branch is
+currently checked out) does not have all commits from test branch.
Notes
--
1.5.3.5
next prev parent reply other threads:[~2007-11-17 19:52 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-13 14:25 [Newbie] How to *actually* get rid of remote tracking branch? Sergei Organov
2007-11-13 14:53 ` Jakub Narebski
2007-11-13 15:39 ` Sergei Organov
2007-11-13 16:01 ` Johannes Schindelin
2007-11-13 17:31 ` Sergei Organov
2007-11-13 18:21 ` Johannes Schindelin
2007-11-13 18:44 ` Sergei Organov
2007-11-17 16:56 ` Jan Hudec
2007-11-13 16:03 ` Jakub Narebski
2007-11-13 17:16 ` Steffen Prohaska
2007-11-13 17:42 ` Jakub Narebski
2007-11-13 17:58 ` osv
2007-11-13 18:17 ` Lars Hjemli
2007-11-13 18:59 ` Sergei Organov
2007-11-13 18:39 ` Steffen Prohaska
2007-11-17 19:12 ` Jan Hudec
2007-11-17 19:51 ` Jan Hudec [this message]
2007-11-19 9:49 ` [PATCH] Improve description of git-branch -d and -D in man page Sergei Organov
2007-11-13 17:47 ` [Newbie] How to *actually* get rid of remote tracking branch? Sergei Organov
2007-11-13 20:01 ` Andreas Ericsson
2007-11-13 22:33 ` Andreas Ericsson
2007-11-13 22:42 ` Jakub Narebski
2007-11-13 23:05 ` J. Bruce Fields
2007-11-13 23:56 ` Junio C Hamano
2007-11-14 1:02 ` Andreas Ericsson
2007-11-14 5:48 ` Steffen Prohaska
2007-11-13 17:40 ` Sergei Organov
2007-11-13 19:17 ` Jakub Narebski
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=20071117195144.GF5198@efreet.light.src \
--to=bulb@ucw.cz \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.com \
--cc=osv@javad.com \
--cc=prohaska@zib.de \
/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).