From: Carl Worth <cworth@cworth.org>
To: Adam Plaice <plaice.adam+notmuch@gmail.com>, notmuch@notmuchmail.org
Subject: Re: Fetching from the git repositories over https?
Date: Fri, 09 Feb 2018 19:11:12 -0800 [thread overview]
Message-ID: <87fu69o7xr.fsf@wondoo.home.cworth.org> (raw)
In-Reply-To: <CAJw81dZ4kzHukW1nycs0CJVQn2cpD19daqjRUXNn5vzbhoiBSA@mail.gmail.com>
On Sun, Jan 28 2018, Adam Plaice wrote:
> I apologise if I'm asking in the wrong place.
Not at all. This is the right place.
> Is it possible to clone/fetch from the notmuch git repositories
> (particularly https://git.notmuchmail.org/git/notmuch) over https
> rather than with the `git://' protocol? (None of the likely
> alternatives seem to work.)
It wasn't possible when you asked, but I just configured this, and it
seems to work.
Specifically, I have tested that I can point my browser at:
https://git.notmuchmail.org/git/notmuch
to see the gitweb view of the git history on the web, and I can also use
that same URL for a git clone:
git clone https://git.notmuchmail.org/git/notmuch
and that works.
I also verified that I a "git push" from such a clone results in a 403
error as desired.
So give that a try, and anyone, let me know if you see anything that I
may have broken or setup incorrectly.
Also, I haven't yet updated any documentation to point to this new
mechanism, so that's something that could still be done.
> Thank you for your time and thank you for notmuch,
You're quite welcome. And thank you for your contribution!
-Carl
next prev parent reply other threads:[~2018-02-10 3:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-28 17:26 Fetching from the git repositories over https? Adam Plaice
2018-02-04 3:10 ` Daniel Kahn Gillmor
2018-02-09 6:28 ` Adam Plaice
2018-02-09 17:42 ` Daniel Kahn Gillmor
2018-02-10 4:34 ` Adam Plaice
2018-02-10 3:11 ` Carl Worth [this message]
2018-02-10 4:37 ` Adam Plaice
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=87fu69o7xr.fsf@wondoo.home.cworth.org \
--to=cworth@cworth.org \
--cc=notmuch@notmuchmail.org \
--cc=plaice.adam+notmuch@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).