From: Adam Plaice <plaice.adam+notmuch@gmail.com>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Cc: notmuch@notmuchmail.org, Carl Worth <cworth@cworth.org>
Subject: Re: Fetching from the git repositories over https?
Date: Sat, 10 Feb 2018 04:34:58 +0000 [thread overview]
Message-ID: <CAJw81dYLCc6nARSo6typhU78PdVFUW-7TBse2sfw7iBFR0Q3gw@mail.gmail.com> (raw)
In-Reply-To: <87o9kyt5zi.fsf@fifthhorseman.net>
> Thanks for doing that! If you need any backup in the discussion, or if
> you think that your suggestion is not being taken as seriously as is
> warranted, i'd be happy to try to help explain the issues to the MELPA
> folks -- contact me directly offlist if you want to coordinate on this.
Thanks for the offer! FWIW, I've opened an issue here:
https://github.com/melpa/melpa/issues/5294
> I think if you use the github mirror, you might just be pushing off
> cleartext fetching to someone else, since that mirror appears to be
> synced over http itself :/ I don't actually know who maintains that
> mirror, and i don't know how to update where it syncs from...
I had been hoping that the mirror was updated by a notmuch contributor
who had access to the main repository and could fetch the code over ssh,
though in any case this is now irrelevant.
> However, Carl Worth (in Cc) just mentioned on IRC that he set up https
> for the official notmuch repo! So please use this URL:
> https://git.notmuchmail.org/git/notmuch
> Thanks Carl! :)
That's brilliant. Thanks very much (and thanks Carl)!
Adam
next prev parent reply other threads:[~2018-02-10 4:35 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 [this message]
2018-02-10 3:11 ` Carl Worth
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=CAJw81dYLCc6nARSo6typhU78PdVFUW-7TBse2sfw7iBFR0Q3gw@mail.gmail.com \
--to=plaice.adam+notmuch@gmail.com \
--cc=cworth@cworth.org \
--cc=dkg@fifthhorseman.net \
--cc=notmuch@notmuchmail.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.
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).