From: Michael J Gruber <git@grubix.eu>
To: Anton Khirnov <anton@khirnov.net>,
Patrick Totzke <patricktotzke@gmail.com>,
notmuch@notmuchmail.org
Subject: Re: announce: my fork of alot
Date: Mon, 17 May 2021 09:33:13 +0200 [thread overview]
Message-ID: <162123679339.5529.18362402287240859724.git@grubix.eu> (raw)
In-Reply-To: <162123531198.470262.5054992432062639445@piu>
Patrick Totzke venit, vidit, dixit 2021-05-17 09:08:31:
> ```
> [~] git clone https://git.khirnov.net/alot.git
> Cloning into 'alot'...
> fatal: unable to access 'https://git.khirnov.net/alot.git/': server certificate verification failed. CAfile: none CRLfile: none
> [~] git clone git://git.khirnov.net/alot.git
>
> Cloning into 'alot'...
>
> (times out)
> ```
It is unauthenticated git protocol:
git clone git://git.khirnov.net/alot.git
I can fully understand why someone wants to host their personal stuff
for themselves. I still don't understand why a git-fork of a
github-project which asks for upstreaming or collaboration is not at
github - and yes, you can 's/github/yourchoice/' in that sentence ;)
Cheers
Michael
next prev parent reply other threads:[~2021-05-17 7:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-16 10:19 announce: my fork of alot Anton Khirnov
2021-05-16 11:15 ` Michael J Gruber
2021-05-16 14:42 ` Anton Khirnov
2021-05-16 15:41 ` Patrick Totzke
2021-05-16 17:47 ` Anton Khirnov
2021-05-16 18:23 ` Patrick Totzke
2021-05-17 7:08 ` Patrick Totzke
2021-05-17 7:33 ` Michael J Gruber [this message]
2021-05-17 7:54 ` Michael J Gruber
2021-05-17 8:25 ` Anton Khirnov
2021-05-17 8:19 ` Anton Khirnov
2021-05-17 8:28 ` Patrick Totzke
2021-05-17 8:39 ` Anton Khirnov
2021-05-17 9:02 ` Anton Khirnov
2021-05-16 22:09 ` Johannes Larsen
2021-05-16 22:32 ` Felipe Contreras
2021-05-16 23:13 ` Johannes Larsen
2021-05-17 0:23 ` Felipe Contreras
2021-05-17 8:54 ` Anton Khirnov
2021-05-17 12:32 ` Johannes Larsen
2021-05-17 12:55 ` Anton Khirnov
2021-05-17 19:03 ` Johannes Larsen
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: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=162123679339.5529.18362402287240859724.git@grubix.eu \
--to=git@grubix.eu \
--cc=anton@khirnov.net \
--cc=notmuch@notmuchmail.org \
--cc=patricktotzke@gmail.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.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).