From: David Bremner <david@tethera.net>
To: Notmuch Mail <notmuch@notmuchmail.org>
Subject: the present and future of patch tracking for notmuch.
Date: Sun, 13 Nov 2011 10:53:40 -0400 [thread overview]
Message-ID: <8762io5b0r.fsf@zancas.localnet> (raw)
[-- Attachment #1: Type: text/plain, Size: 1371 bytes --]
As some of you probably know, I have been using "nmbug" [1], now in git
master, to help track the state of notmuch patches. At this point I
think I am about ready to declare the experimental deployment of nmbug a
success and make it more official.
## present?
- Currently this is running off a git repo on my server. I don't really
mind doing this, but it would probably reduce confusion to have the
"the" repo on git.notmuchmail.org
- Currently I am controlling push access to the nmbug repo by ssh-key.
This is not really a burden, but I wonder if it would be better to
allow anonymous pushes, perhaps to some staging repo that trusted
people (i.e. those with ssh keys) could pull from.
## future?
- It would be nice if people without notmuch installed had access to the
information. Some way to make html dumps of threads with tags would
do the trick, I believe. So far I am resisting the temptation to write
such a thing.
- I'm not sure about the future of the notmuch patchwork instance. It
doesn't hurt anything, but it does consume resources, and maybe
generate confusion.
- So far, I'm continuing to post messages about pushed patches to the
list. If at some point the consensus is that this is more annoying
than useful, I'm perfectly willing to stop.
d
[1]: http://notmuchmail.org/nmbug
[-- Attachment #2: Type: application/pgp-signature, Size: 315 bytes --]
next reply other threads:[~2011-11-13 14:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-13 14:53 David Bremner [this message]
2011-11-15 15:19 ` the present and future of patch tracking for notmuch David Bremner
2011-12-15 12:05 ` David Bremner
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=8762io5b0r.fsf@zancas.localnet \
--to=david@tethera.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).