All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergey Organov <sorganov@gmail.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
	Chris Torek <chris.torek@gmail.com>,
	Hongyi Zhao <hongyi.zhao@gmail.com>,
	Phillip Susi <phill@thesusis.net>, Git List <git@vger.kernel.org>
Subject: Re: git revert with partial commit.
Date: Fri, 07 Apr 2023 20:20:11 +0300	[thread overview]
Message-ID: <87mt3jbodw.fsf@osv.gnss.ru> (raw)
In-Reply-To: CAMP44s32nLHCZmWQ3V5sBL6WZA9qqWXi86c+=Bxt+GQ8fPmFfQ@mail.gmail.com

Felipe Contreras <felipe.contreras@gmail.com> writes:

> On Wed, Apr 5, 2023 at 1:39 AM Sergey Organov <sorganov@gmail.com>
> wrote:
>> Felipe Contreras <felipe.contreras@gmail.com> writes:
>
>> > If the user wants to do it, the tool should help him do it, not
>> > pontificate about what is heretic.
>> > The user is still going to do it, like with a rebase plugin on
>> > Mercurial, or with `git filter-branch` and then merge the result.
>> > All the tool is achieving is being annoying by not helping the
>> > user.
>> Yep, and I'm worried by such trends in Git as well. Looks like
>> growing influence of software development culture where the user is
>> not considered to be intelligent enough to make proper decisions by
>> himself, and needs to be thoroughly guided by the tool (designers)
>> all the time.
>
> Which ironically goes against the philosophy of the original author of
> Git:
>
>> No project is more important than the users of the project.
>> -- Linus Torvalds

I rather bother about too much care for the users in the aforementioned
cases, similar to the way overly cautious mother cares about her
children, all this being absolutely well-intentioned.

The problem with such care is that it's inefficient to drive nails in
with a hand hammer in a soft wrapping, though it's admittedly less
dangerous for ones fingers.

Overall, when using a tool, I prefer to feel myself a grown-up human
being responsible for my own actions, rather than a child under intense
guidance and excessive protection. I'm thankful for proper safety
measures, but I want potentially unsafe action to be performed
nevertheless when I actually mean it, instead of lengthy display of
rhetorics about why I should not have had even attempted it in the first
place.

-- 
Sergey Organov

  reply	other threads:[~2023-04-07 17:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-02  9:17 git revert with partial commit Hongyi Zhao
2023-04-02 14:16 ` Torsten Bögershausen
2023-04-03 17:07   ` Junio C Hamano
2023-04-04  0:28   ` Hongyi Zhao
2023-04-03 18:29 ` Phillip Susi
2023-04-04  0:20   ` Hongyi Zhao
2023-04-04  0:37     ` Hongyi Zhao
2023-04-04 15:50       ` Hongyi Zhao
2023-04-04 16:19         ` Chris Torek
2023-04-04 17:21           ` Sergey Organov
2023-04-04 18:20             ` Junio C Hamano
2023-04-04 19:40               ` Sergey Organov
2023-04-04 19:48                 ` Junio C Hamano
2023-04-04 21:14                 ` Felipe Contreras
2023-04-05  6:39                   ` Sergey Organov
2023-04-07  0:24                     ` Felipe Contreras
2023-04-07 17:20                       ` Sergey Organov [this message]
2023-04-06 15:48     ` Phillip Susi

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=87mt3jbodw.fsf@osv.gnss.ru \
    --to=sorganov@gmail.com \
    --cc=chris.torek@gmail.com \
    --cc=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=hongyi.zhao@gmail.com \
    --cc=phill@thesusis.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.