public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
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
Subject: Re: [Newbie] How to *actually* get rid of remote tracking branch?
Date: Sat, 17 Nov 2007 20:12:56 +0100	[thread overview]
Message-ID: <20071117191256.GD5198@efreet.light.src> (raw)
In-Reply-To: <87d4ue81tv.fsf@osv.gnss.ru>

[-- Attachment #1: Type: text/plain, Size: 1027 bytes --]

On Tue, Nov 13, 2007 at 20:58:20 +0300, osv@javad•com wrote:
> Guys, could you please read man git-branch? What do you think this
> example is doing?:
> 
> <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.

-- 
						 Jan 'Bulb' Hudec <bulb@ucw•cz>

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2007-11-17 19:13 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 [this message]
2007-11-17 19:51               ` [PATCH] Improve description of git-branch -d and -D in man page Jan Hudec
2007-11-19  9:49                 ` 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=20071117191256.GD5198@efreet.light.src \
    --to=bulb@ucw$(echo .)cz \
    --cc=git@vger$(echo .)kernel.org \
    --cc=jnareb@gmail$(echo .)com \
    --cc=osv@javad$(echo .)com \
    --cc=prohaska@zib$(echo .)de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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