git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Philip Oakley <philipoakley@iee.email>
To: _g e r r y _ _l o w r y _ 
	<gerry.lowry@abilitybusinesscomputerservices.com>,
	'Filip Lipien' <aaa@164.ooo>
Cc: git@vger.kernel.org, torvalds@linux-foundation.org
Subject: Re: Request to remove Junio C Hamano as the Git Maintainer
Date: Tue, 3 Jan 2023 13:25:12 +0000	[thread overview]
Message-ID: <d84712ed-1504-4d54-a664-63713db570b6@iee.email> (raw)
In-Reply-To: <064601d91f0e$b5521940$1ff64bc0$@abilitybusinesscomputerservices.com>

On 03/01/2023 00:59, _g e r r y _ _l o w r y _ wrote:
> Git stands head and shoulders above other versioning software products;
> the reason is that Linus designed a superior system.

I don't think that ("superior") is quite true, in the same way that
'world class' and 'best practice' don't have the meaning they hope to
convey ;-)

However, what Linus managed to do was to cut the Gordian Knot of the
historical versioning systems that had their original designs created in
the quill pen era, and are totally unsuited for the modern, high speed
computation and perfect replication digital age. Finally, I have control
over my versioning system (at least for software)!

In some ways, Git is like the 'Coming of the Railways'. It has brought
radical change, but at the same time, confusion, reorganisation and new
ways of thinking and working.


*Filip* has accidentally fallen into the attribution trap of blaming the
maintainer, rather than having an analysis and reflection on how Git is
being used in different user contexts. His user context may have
alternate expectations to that of the Linux eco-system, but that doesn't
excuse the lack of self reflection.

--
Philip

  reply	other threads:[~2023-01-03 13:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-31 18:11 Request to remove Junio C Hamano as the Git Maintainer Filip Lipien
2022-12-31 19:19 ` Theodore Ts'o
2022-12-31 23:23   ` Filip Lipien
2023-01-01 12:59     ` Philip Oakley
2022-12-31 22:08 ` rsbecker
2023-01-01 21:10 ` brian m. carlson
2023-01-02  3:37   ` Theodore Ts'o
2023-01-03  0:59 ` _g e r r y _ _l o w r y _
2023-01-03 13:25   ` Philip Oakley [this message]
2023-01-03 15:08     ` Konstantin Khomoutov
2023-01-11 17:23       ` Rudy Rigot
2023-01-03  9:45 ` demerphq
2023-01-12  9:30   ` Ævar Arnfjörð Bjarmason
2023-01-12 16:48     ` Rudy Rigot

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d84712ed-1504-4d54-a664-63713db570b6@iee.email \
    --to=philipoakley@iee.email \
    --cc=aaa@164.ooo \
    --cc=gerry.lowry@abilitybusinesscomputerservices.com \
    --cc=git@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).