public inbox for mlmmj@mlmmj.org
 help / color / mirror / Atom feed
From: Richard Mortimer <richm@oldelvet.org.uk>
To: mlmmj@mlmmj.org
Subject: Re: [mlmmj] New mlmmj website and development
Date: Wed, 26 Jan 2011 14:32:21 +0000	[thread overview]
Message-ID: <4D403075.6070105@oldelvet.org.uk> (raw)
In-Reply-To: <4C680191.506@yahoo.com.au>

On 15/08/2010 16:02, Ben Schmidt wrote:
> Hi, everybody,
>
> I'm pleased to announce that the new mlmmj website is up and running! I
> encourage you to have a look at it. Anyone interested in having an
> account to be able to help maintain it, please let me know! It's where
> it's always been: http://mlmmj.org/
>
> This includes a bug tracker. I will be adding bugs and feature requests
> that I know about over the next few days, and I encourage others to do
> so also. My next priority is working towards a release that includes
> recently-implemented features as well as minor bug fixes, so I'm
> interested in hearing about as many bugs as we know about. The tracker
> is here: http://mlmmj.org/bugs

Hi Ben,

Thanks for your efforts. I've been using mlmmj for a while now and it 
works pretty well. I have noticed a few little annoyances that I haven't 
really followed up until now but I'd like to change that and help where 
I can.

For instance yesterday I was trying to find an issue where I was not 
getting notified of unsubscriptions due to bouncing. In the end it 
turned out to be me having the wrong list control directory settings for 
one of my lists. I'll try to take a look through my notebook and see if 
I can come up with a list of these "annoyances".

However whilst I was looking for the cause of my problem I spent a bit 
of time looking through mlmmj-maintd.c to trace what it was supposed to 
be doing at each step. Whilst doing this I spotted a number of minor 
issues in the mlmmj-maintd.c code.

With that in mind I would be grateful if you could let me know your 
preferred way of working/review. I could just post the patches to the 
mailing list (in hg email format). I'm a little concerned that testing 
some of these changes is going to be difficult because they do involve a 
number of corner cases that shouldn't happen in normal operation. Most 
changes are fairly small however and IMHO they will add value to the 
long term stability of mlmmj.

If patches are of interest and do prove useful I'll see if I can find 
some time to review other parts of mlmmj over the next month or two.

Let me know your preferred way of working because I'm wary of sending a 
chunk of patches to a mailing list unannounced.

Regards

Richard


  parent reply	other threads:[~2011-01-26 14:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-15 15:02 [mlmmj] New mlmmj website and development Ben Schmidt
2010-09-07 13:28 ` Mads Martin Jørgensen
2011-01-26 14:32 ` Richard Mortimer [this message]
2011-01-26 14:49 ` Mads Martin Jørgensen
2011-01-27  3:52 ` Ben Schmidt

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=4D403075.6070105@oldelvet.org.uk \
    --to=richm@oldelvet.org.uk \
    --cc=mlmmj@mlmmj.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