From: Doug Henderson <djndnbvg@gmail.com>
To: Cygwin Apps <cygwin-apps@cygwin.com>
Subject: Re: github password policy
Date: Mon, 16 Aug 2021 17:59:35 -0600 [thread overview]
Message-ID: <CAJ1FpuNEUwQnxCC9=KEqqe3n-0oh2aLvn5qPizSANUtP534eVw@mail.gmail.com> (raw)
In-Reply-To: <87r1etmrlz.fsf@Otto.invalid>
On Mon, 16 Aug 2021 at 07:45, ASSI <Stromeko@nexgo.de> wrote:
>
> Thomas Wolff writes:
> > As I cannot update mintty anymore right now from the git command line,
Yes, I use SSH for all repos now.
> Do. Not. Use. GitHub.
>
> The raison raison d'être for GitHub is and always has been to subvert
> the fully distributed workflow that Git was designed to provide and
> replace it with their centralized lock-in "solution".
As well as GidHub for several public repos, I have used BitBucket for
several private repositories, as they allowed several, while GitHub
only allowed one. They also have a large number of add on features
around the Git repositories, aimed at lock-in.
Does anyone have online Git servers they use and can recommend? BTW, I
have done Google searches, etc. I'm looking for enthusiastic personal
endorsements.
Doug
--
Doug Henderson, Calgary, Alberta, Canada - from gmail.com
next prev parent reply other threads:[~2021-08-16 23:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-16 12:13 Thomas Wolff
2021-08-16 13:44 ` ASSI
2021-08-16 23:59 ` Doug Henderson [this message]
2021-08-17 3:00 ` Brian Inglis
2021-08-18 17:12 ` Thomas Wolff
2021-08-16 14:44 ` Corinna Vinschen
2021-08-16 14:46 ` Lee
2021-08-16 17:51 ` Thomas Wolff
2021-08-16 17:59 ` Yaakov Selkowitz
2021-08-17 6:39 ` Thomas Wolff
2021-08-16 18:33 ` Jonathan Yong
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='CAJ1FpuNEUwQnxCC9=KEqqe3n-0oh2aLvn5qPizSANUtP534eVw@mail.gmail.com' \
--to=djndnbvg@gmail.com \
--cc=cygwin-apps@cygwin.com \
/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 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).