All of lore.kernel.org
 help / color / mirror / Atom feed
From: "_g e r r y _ _l o w r y _"  <gerry.lowry@abilitybusinesscomputerservices.com>
To: "'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: Mon, 2 Jan 2023 19:59:49 -0500	[thread overview]
Message-ID: <064601d91f0e$b5521940$1ff64bc0$@abilitybusinesscomputerservices.com> (raw)
In-Reply-To: <7hfRSnKTRnT4uJh5Pok8U8gfLm_NXzCS6w_7_Rc9OH3a9Lv8hpjySZqxDglBFC-fTOdZHi-ODCihiEHlQD9nIhUmld5jYvRx_JvB0z2IAL0=@164.ooo>

Filip, maintaining software is a big responsibility; 
       if Git were easy, maintaining would still be work.

is it Junio's fault that there a so many questions on SO?

Git stands head and shoulders above other versioning software products;
the reason is that Linus designed a superior system.

You might find Git easier to use from these links:

whether first learning Git, or reviewing what one already knows, I very strongly recommends that one starts here:
Git :: 4 short introductory videos from https://git-scm.com/doc
Total running time c. 25'
https://git-scm.com/video/what-is-version-control
https://git-scm.com/video/what-is-git
https://git-scm.com/video/get-going
https://git-scm.com/video/quick-wins
4 short introductory videos from https://git-scm.com/doc"
Note:  imho, the 4 short videos above, although limited in content, set the tone and spirit for beginning a friendship with Git; links below actually teach you Git.
"Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency."
https://git-scm.com/


free via Amazon (Kindle Edition):
Ry's Git Tutorial
 By: Ryan Hodson
https://www.amazon.ca/dp/B00QFIA5OC/


21'30"
https://youtu.be/FdZecVxzJbk      Corey Schafer
"Git Tutorial: Fixing Common Mistakes and Undoing Bad Commits"
-- watch this once for an initial overview of what one can do to dig oneself out of a hole.
-- watch this multiple times to become competent


30'32"
https://youtu.be/HVsySz-h9r4      Corey Schafer
"Git Tutorial for Beginners: Command-Line Fundamentals"
BOTTOM LINE:  the command line is a powerful way to use Git.


imho, Git is to version control as Tesla is to VW Beetle.

Filip, sounds to me like you make stuff up, like when you write:
  "The financial damage goes into the billions."


i stay neutral regarding Junio because unless you prove
otherwise, i imagine that Junio is both doing a decent job
and likely not even getting paid for it.

~~Gerry

-----Original Message-----
From: Filip Lipien <aaa@164.ooo> 
Sent: Saturday, December 31, 2022 13:11
To: git@vger.kernel.org
Cc: torvalds@linux-foundation.org
Subject: Request to remove Junio C Hamano as the Git Maintainer

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.

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.

I hereby request the removal of Junio C Hamano 濱野純 as the Git Maintainer.


  parent reply	other threads:[~2023-01-03  1:05 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 _ [this message]
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='064601d91f0e$b5521940$1ff64bc0$@abilitybusinesscomputerservices.com' \
    --to=gerry.lowry@abilitybusinesscomputerservices.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.