Re: Question about 'branch -d' safety
- From
Matthieu Moy <matthieu.moy@grenoble-inp.fr>
- Date
- Jul 20, 2010, 13:34 UTC
- Message-ID
- <vpq630a5lb5.fsf@bauges.imag.fr>
- In-Reply-To
- <AANLkTilOhFqhg1ulWEZUceNmrf0djZti9E1Y2QzTRgaN@mail.gmail.com>
Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
Show 16 quoted lines
> On Mon, Jul 19, 2010 at 18:06, Junio C Hamano <gitster@pobox.com> wrote: >> Clemens Buchacher <drizzd@aon.at> writes: >> >>> Pros and cons for "undeleting branches": >>> >>> + safety net >>> It should not be easy to lose information with git. >> >> I am personally not very convinced by this argument when it comes to the >> cases where the user actively asks us to remove something. > > [...] > > As Will Palmer pointed out, being able to tell newbies "Don't worry, > you aren't going to break it" is a very powerful thing to be able to > tell newbies and experienced users using Git.
Also, one of the _very_ cool things with Git is that advance users can tell newbies "don't worry, if you break it, I'll be able to repair it". And advanced users are almost always able to repair beginner's mistake after the fact (in my case, it's often about teachers helping students, but it works also in other situations).
"branch -d" (and even more "branch -D") deleting the reflog is one of the few exceptions to this rule: dumb users can shoot themselves in the foot (which is normal) but then the doctor cannot undo it easily.
-- Matthieu Moy http://www-verimag.imag.fr/~moy/