Preparing hypermail cvs commit/merge, suggestions?

---------

From: jose.kahan@w3.org
Date: Fri Sep 03 1999 - 10:45:55 CDT


Daniel, folks,

I finished merging my patches into the latest hypermail out from CVS.
I have many patches that fix or add new features:

- Handling of Content-Disposition headers
- Metadata (plus config/command line options to turn it on)
- New option for turning off hypermail's locking mechanism (e.g., Smartlist
  provides a better mechanism, so I don't need hypermail's one)
- Some fixes on the MIME handler for RFC822 attachments
- Counter policy for MIME attachments (nn-fname or nn-part) as described
  in an earlier mail

BTW, I'm not sure on how to update the man files (.4). Just edit them
and add the new options?

My tests work out well. However, I may have missed something or
broke something else. I'm only using a handful of the config file options.

How would you like me to proceed to make this merge commit? I see two
options:

- Someone volunteers (Paul?) to run my hypermail on some of his files and
  see if he has the same result. If it's ok, I'll commit my changes then

- I commit my changes to the base and fix any bugs that may appear from them
  as they are reported.

I don't know how many parallel hypermail developments are taking place
right now, but if you're working on the parse.c file, you'll have a
good CVS time after the commit (47 differences).

Following a known developer's rule, I won't make this commit before Monday
and before receiving a go-ahead from the other developers/users.

Next in my to-do list:

* continue testing/improving RFC822 parsing
* parsing of MH mboxes

Bon weekend,

-Jose


---------

This archive was generated by hypermail 2.1.5.