unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: a temporary nmweb view of notmuch mailing list archive
Date: Thu, 08 Feb 2018 23:28:00 -0500	[thread overview]
Message-ID: <87a7wivlbj.fsf@fifthhorseman.net> (raw)
In-Reply-To: <87o9l4yt4w.fsf@fifthhorseman.net>

[-- Attachment #1: Type: text/plain, Size: 976 bytes --]

On Sun 2018-02-04 23:09:35 -0500, Daniel Kahn Gillmor wrote:

> I did a bit of experimenting with Brian Sniffen's proposed notmuch-web
> branch, and it's now (temporarily) publishing a view of the notmuch
> mailing list here:
>
>     https://nmbug.notmuchmail.org/btsmail/
>
> I DO NOT EXPECT THIS URL TO BE STABLE -- please do not use links to it
> in permanent places, this is just for experimentation at the moment.

this is gradually getting better.  new messages to the list are
automatically archived and visible here, and the archive doesn't
spontaneously break in ways i can't predict.

it does still break every time an authorized user does "nmbug push"
though, and i don't currently understand why.  I'm putting in place a
workaround for it but if anyone has suggestions for debugging it
server-side, i'm all ears.  nmbug is backed server-side by gitolite, and
i don't know gitolite well enough to know how it sets umask or
permissions by default.

           --dkg

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2018-02-09  4:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-05  4:09 a temporary nmweb view of notmuch mailing list archive Daniel Kahn Gillmor
2018-02-09  4:28 ` Daniel Kahn Gillmor [this message]
2018-02-10 18:57   ` Brian Sniffen
2018-02-11 20:03     ` Daniel Kahn Gillmor
2018-02-15 16:06       ` Daniel Kahn Gillmor
2018-02-15 20:47         ` Brian Sniffen
2018-02-15 23:42           ` Daniel Kahn Gillmor
2018-02-13  5:47 ` Carl Worth
2018-02-13 16:56   ` J. Lewis Muir

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=87a7wivlbj.fsf@fifthhorseman.net \
    --to=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).