From: "Martin Liška" <mliska@suse.cz>
To: Overseers mailing list <overseers@sourceware.org>
Subject: Re: mailman customization not quite right yet
Date: Sat, 4 Apr 2020 11:20:06 +0200 [thread overview]
Message-ID: <001a2bc5-2fc3-c5de-7918-06b587668445@suse.cz> (raw)
In-Reply-To: <20200403205254.GA12086@cgf.cx>
On 4/3/20 10:52 PM, Christopher Faylor wrote:
> On Fri, Apr 03, 2020 at 12:42:45PM -0400, Christopher Faylor wrote:
>> I'll generate this rpm + patches along with instructions on how to do it
>> in the future.
>
> I tried testing the, I think, least intrusive part of this patch set:
>
> diff --git a/templates/en/archidxentry.html b/templates/en/archidxentry.html
> index f9bb57a..365e836 100644
> --- a/templates/en/archidxentry.html
> +++ b/templates/en/archidxentry.html
> @@ -1,3 +1,5 @@
> +<I>%(datestr)s
> +</I>
> <LI><A HREF="%(filename)s">%(subject)s
> </A><A NAME="%(sequence)i"> </A>
> <I>%(author)s
>
> It didn't work right after regenerating the test-list archive. It
> resulted in a web page that looked like (cut from the web page):
>
> 2020 Archives by date
>
> Messages sorted by: [ thread ] [ subject ] [ author ]
> More info on this list...
>
> Starting: Sun Feb 9 02:40:00 GMT 2020
> Ending: Fri Apr 3 17:28:10 GMT 2020
> Messages: 37
>
> >>>> %(datestr)s <<<<
> Test Christopher Faylor via test-list %(datestr)s
> Inspect headers Christopher Faylor %(datestr)s
>
> i.e., the %{datestr}s is being treated literally. I don't think that
> the template change relies on the rest of the patch so this isn't
> doing what we'd think.
Hello.
Thank you for the testing of my patch! Yes, it looks there's a missing
exported datestr variably.
>
> I do have an rpm built with these changes but it obviously isn't quite
> ready for prime time.
>
> I have been experimenting with adding an extra "recent" entry in the
> mailing list that looks more like ezmlm. You can see it here:
>
> https://sourceware.org/pipermail/test-list/2020/recent.html
>
> When turned on, it adds a "[ recent ]" link to appropriate pages.
> Clicking on mailto's on the summary page open your mailer with the
> mailing list in the To:, the original sender in the Cc: (since I now
> understand that this is really important), and appropriate In-Reply-To's
> to maintain threading.
>
> I accomplish this by running a perl script whenever mailman has finished
> with a "post" operation. The script iterates over the html message
> files to produce an ezmlm-like archive. This isn't perfect yet but I
> thought I'd offer it as a possible alternative to patching mailman.
... but I must confirm that this looks nice and I bet other people will
like it as well. I support that.
Thanks,
Martin
>
> cgf
>
next prev parent reply other threads:[~2020-04-04 9:20 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <C92C61E7-EF8A-4AD7-904D-FA6E0AD6649C@tkoenig.net>
2020-03-09 8:40 ` gcc ML archive: text/x-patch attachments no longer shown inline (was:Re: Mailing list stripping off attachments) Tobias Burnus
2020-03-09 8:48 ` Thomas König
2020-03-09 9:46 ` text/x-* attachments stripped (was: Re: gcc ML archive: text/x-patch attachments no longer shown inline (was:Re: Mailing list stripping off attachments)) Tobias Burnus
2020-03-09 9:51 ` List-Id header being stripped (was:Re: Mailing list stripping off attachments) Richard Bradfield
2020-03-09 10:27 ` List-Id header being stripped Andreas Schwab
2020-03-09 10:44 ` Richard Bradfield
2020-03-09 10:30 ` Florian Weimer
2020-03-09 10:49 ` Richard Earnshaw
2020-03-09 11:32 ` Florian Weimer
2020-03-09 12:28 ` Gerald Pfeifer
2020-03-09 10:25 ` text/x-* attachments stripped (was: Re: gcc ML archive: text/x-patch attachments no longer shown inline (was:Re: Mailing list stripping off attachments)) Jakub Jelinek
2020-03-09 10:47 ` Jonathan Wakely
2020-03-09 11:21 ` text/x-* attachments stripped Andreas Schwab
2020-03-09 13:57 ` text/x-* attachments stripped (was: Re: gcc ML archive: text/x-patch attachments no longer shown inline (was:Re: Mailing list stripping off attachments)) Thomas König
2020-03-09 15:45 ` text/x-* attachments strippe Gerald Pfeifer
2020-03-09 16:03 ` Frank Ch. Eigler
2020-03-09 16:53 ` text/x-* attachments stripped (was: Re: gcc ML archive: text/x-patch attachments no longer shown inline Nathan Sidwell
2020-03-09 17:06 ` Andreas Schwab
2020-03-09 17:07 ` Jonathan Wakely
2020-03-09 17:20 ` text/x-* attachments stripped Nathan Sidwell
2020-03-09 19:49 ` text/x-* attachments stripped (was: Re: gcc ML archive: text/x-patch attachments no longer shown inline (was:Re: Mailing list stripping off attachments)) Thomas König
2020-03-09 22:11 ` Jonathan Wakely
2020-03-09 21:07 ` Joseph Myers
2020-03-09 23:16 ` Jonathan Wakely
2020-04-03 14:29 ` Martin Liška
2020-04-03 15:19 ` Christopher Faylor
2020-04-03 15:43 ` mailman customization Martin Liška
2020-04-03 15:54 ` Frank Ch. Eigler
2020-04-03 15:58 ` Martin Liška
2020-04-03 16:30 ` Christopher Faylor
2020-04-03 16:42 ` Christopher Faylor
2020-04-03 20:52 ` mailman customization not quite right yet Christopher Faylor
2020-04-04 9:20 ` Martin Liška [this message]
2020-05-05 9:57 ` Martin Liška
2020-05-05 14:23 ` Christopher Faylor
2020-04-03 16:36 ` mailman customization Christopher Faylor
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=001a2bc5-2fc3-c5de-7918-06b587668445@suse.cz \
--to=mliska@suse.cz \
--cc=overseers@sourceware.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.
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).