From: Matthieu Moy <Matthieu.Moy@grenoble-inp•fr>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail•com>
Cc: Junio C Hamano <gitster@pobox•com>,
Clemens Buchacher <drizzd@aon•at>,
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>,
Joshua Jensen <jjensen@workspacewhiz•com>
Subject: Re: Question about 'branch -d' safety
Date: Tue, 20 Jul 2010 15:34:22 +0200 [thread overview]
Message-ID: <vpq630a5lb5.fsf@bauges.imag.fr> (raw)
In-Reply-To: <AANLkTilOhFqhg1ulWEZUceNmrf0djZti9E1Y2QzTRgaN@mail.gmail.com> ("Ævar Arnfjörð Bjarmason"'s message of "Tue\, 20 Jul 2010 13\:19\:55 +0000")
Ævar Arnfjörð Bjarmason <avarab@gmail•com> writes:
> 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/
prev parent reply other threads:[~2010-07-20 13:39 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
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 [this message]
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=vpq630a5lb5.fsf@bauges.imag.fr \
--to=matthieu.moy@grenoble-inp$(echo .)fr \
--cc=avarab@gmail$(echo .)com \
--cc=drizzd@aon$(echo .)at \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=jjensen@workspacewhiz$(echo .)com \
--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