From: Sergei Organov <osv@javad.com>
Date: Mon, 19 Nov 2007 09:49:54 GMT
Subject: Re: [PATCH] Improve description of git-branch -d and -D in man page.
Message-ID: <877ike1s59.fsf@osv.gnss.ru>
In-Reply-To: <20071117195144.GF5198@efreet.light.src>

Jan Hudec <bulb@ucw.cz> writes:
> 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?

Yes, I think now it describes the actual behavior much much better, --
thanks.

-- 
Sergei.