From: Junio C Hamano <gitster@pobox•com>
To: Clemens Buchacher <drizzd@aon•at>
Cc: Jakub Narebski <jnareb@gmail•com>,
Jonathan Nieder <jrnieder@gmail•com>,
git@vger•kernel.org, Nicolas Sebrecht <nicolas.s.dev@gmx•fr>,
Nanako Shiraishi <nanako3@lavabit•com>
Subject: Re: Question about 'branch -d' safety
Date: Mon, 12 Jul 2010 16:50:32 -0700 [thread overview]
Message-ID: <7v39vo8dkn.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20100712184754.GA18429@localhost> (Clemens Buchacher's message of "Mon\, 12 Jul 2010 20\:47\:55 +0200")
Clemens Buchacher <drizzd@aon•at> writes:
>> What problem are you guys really trying to solve?
>
> The reflog protects you from almost all involuntary loss of
> information.
And you call "git branch -[dD]" involuntary?
I am not entirely unsympathetic to add "git branch --undelete frotz" to our
vocabulary, but then we should leave users an easy way to really remove
things, and it shouldn't be "git branch -d --i-really-mean-it frotz".
It would probably be more like "git branch -d frotz" followed by "git
branch --purge frotz" or "git branch --purge \*" (if we name the operation
to remove cruft for undelete "purge", that is).
next prev parent reply other threads:[~2010-07-12 23:50 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-29 21:54 Question about 'branch -d' safety Nanako Shiraishi
2009-12-29 22:31 ` Nicolas Sebrecht
2009-12-30 3:12 ` Nanako Shiraishi
2009-12-30 6:43 ` Junio C Hamano
2009-12-30 21:08 ` Nicolas Sebrecht
2010-07-10 6:55 ` Clemens Buchacher
2010-07-10 21:40 ` Jonathan Nieder
2010-07-10 21:57 ` Jakub Narebski
2010-07-10 22:17 ` Jonathan Nieder
2010-07-11 6:55 ` Clemens Buchacher
2010-07-11 7:16 ` Jakub Narebski
2010-07-11 8:48 ` Julian Phillips
2010-07-11 13:37 ` Clemens Buchacher
2010-07-11 18:41 ` Junio C Hamano
2010-07-11 19:05 ` Jakub Narebski
2010-07-11 22:02 ` Will Palmer
2010-07-12 18:47 ` Clemens Buchacher
2010-07-12 23:50 ` Junio C Hamano [this message]
2010-07-13 7:13 ` Clemens Buchacher
2010-07-13 8:00 ` Will Palmer
2010-07-13 8:30 ` Johannes Sixt
2010-07-13 9:00 ` Will Palmer
2010-07-13 22:21 ` Clemens Buchacher
2010-07-17 9:30 ` Clemens Buchacher
2010-07-18 0:43 ` Jonathan Nieder
2010-07-18 11:55 ` Jakub Narebski
2010-07-18 20:27 ` Will Palmer
2010-07-18 23:19 ` Jakub Narebski
2010-07-19 7:12 ` Will Palmer
2010-07-19 11:01 ` Jakub Narebski
2010-07-19 17:16 ` Joshua Jensen
2010-07-19 19:34 ` Clemens Buchacher
2010-07-19 19:45 ` Will Palmer
2010-07-19 20:40 ` Jakub Narebski
2010-07-20 3:05 ` Joshua Jensen
2010-07-20 6:31 ` Will Palmer
2010-07-19 20:36 ` Jakub Narebski
2010-07-19 18:06 ` Junio C Hamano
2010-07-19 19:22 ` Clemens Buchacher
2010-07-19 20:49 ` Jakub Narebski
2010-07-20 13:19 ` Ævar Arnfjörð Bjarmason
2010-07-20 13:34 ` Matthieu Moy
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=7v39vo8dkn.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox$(echo .)com \
--cc=drizzd@aon$(echo .)at \
--cc=git@vger$(echo .)kernel.org \
--cc=jnareb@gmail$(echo .)com \
--cc=jrnieder@gmail$(echo .)com \
--cc=nanako3@lavabit$(echo .)com \
--cc=nicolas.s.dev@gmx$(echo .)fr \
/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