From: <rsbecker@nexbridge.com>
To: "'Filip Lipien'" <aaa@164.ooo>, <git@vger.kernel.org>
Cc: <torvalds@linux-foundation.org>
Subject: RE: Request to remove Junio C Hamano as the Git Maintainer
Date: Sat, 31 Dec 2022 17:08:39 -0500 [thread overview]
Message-ID: <001201d91d64$732e4e90$598aebb0$@nexbridge.com> (raw)
In-Reply-To: <7hfRSnKTRnT4uJh5Pok8U8gfLm_NXzCS6w_7_Rc9OH3a9Lv8hpjySZqxDglBFC-fTOdZHi-ODCihiEHlQD9nIhUmld5jYvRx_JvB0z2IAL0=@164.ooo>
On December 31, 2022 1:11 PM, Filip Lipien wrote:
>There are more than one million questions on Stackoverflow related to the usage
>of Git.
>This is not normal.
>
>Git is in its current state not a tool that's made for humans.
Git is used by hundreds of thousands to millions of humans on a daily basis. It manages most of the popular operating system code and compilers and without git, CI/CD would (arguably) be where it was 20 years ago. Git is part of a critical supply chain, including automation, to deliver software to production servers and edge devices.
>It's realistic to assume, that millions of working hours were wasted due to his
>ignorance of developer experience.
>The financial damage goes into the billions.
Claims like this require extraordinary evidence; rather like claiming aliens are hacking our git repositories (they are not).
>I hereby request the removal of Junio C Hamano 濱野純 as the Git Maintainer.
I hereby strongly support Junio's continued participation and hope he is not disheartened by the OP request.
Randall
--
Brief whoami: NonStop&UNIX developer since approximately
UNIX(421664400)
NonStop(211288444200000000)
-- In real life, I talk too much.
next prev parent reply other threads:[~2022-12-31 22:09 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='001201d91d64$732e4e90$598aebb0$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=aaa@164.ooo \
--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.
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.