user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <>
Subject: [PATCH] TODO: updates based on git@vger mirror experience
Date: Sun, 14 Aug 2016 11:33:20 +0000	[thread overview]
Message-ID: <> (raw)

Plenty more to do!
 TODO | 23 ++++++++++++++++++-----
 1 file changed, 18 insertions(+), 5 deletions(-)

diff --git a/TODO b/TODO
index 644fa03..dfee6e5 100644
--- a/TODO
+++ b/TODO
@@ -47,17 +47,30 @@ all need to be considered for everything we introduce)
 * handle Xapian date range queries:
-* Consider storing git blob ID in Xapian doc data to avoid ref
-  and tree lookups based on Message-Id.
+* handle messages with multiple Message-IDs
+* handle broken double-bracketed References properly (maybe)
+  and totally broken Message-IDs
+  cf.
+* portability to FreeBSD (and other Free Software *BSDs)
+  ugh...
+* documentation (pod/text)
+* linkify thread skeletons better
+* generate sample CSS for use with Stylish/dillo/etc
+* builtin-help for search engine syntax
 * streaming Email::MIME replacement: currently we generate many
   allocations/strings for headers we never look at and slurp
   entire message bodies into memory.
   (this is pie-in-the-sky territory...)
-* Allow in-place Xapian updates without clobbering the whole
-  index (versioning each doc data entry?) for big archives
 * use REQUEST_URI properly for CGI / mod_perl2 compatibility
   with Message-IDs which include '%' (done?)

                 reply	other threads:[~2016-08-14 11:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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 inbox:

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).