First off, let me say that I didn't mean to suggest stepping on anyone's
toes -- I certainly feel that Dan and Doug have done the world a
service, and I respect that. I threw out SF as an option because it
would let us beat on an `interim release' or similar without disturbing
the current mhost
New module? No, that is just not the way CVS is supposed to be
used. Maybe a seperate branch if radical changes are going to be
made, but HEAD is the appropriate place for most development.
Hmm. While I agree with you, and I'm certainly willing to try it, I
have to say that most of the
chad wrote:
I would say that if you are interested and
don't get a response in a reasonable time, a new SourceForge project may
be in order. I'd suggest ``1 January 2002'' as a reasonable cut-off,
Hi all --
How's SourceForge doing these days? VA Software isn't in the best shape
now, I
On Thu, 2001-12-06 at 17:47, chad wrote:
In looking over back mail recently, I noticed that no one responded to
Jon Steinhart's interesting patches regarding mime attachments. If
memory serves, he prodded the list more than once; at least once with no
response in early July. I would say
How's SourceForge doing these days? VA Software isn't in the best shape
now, I hear. I've been trying to find a big chunk of time to move the
online MH book to SourceForge, but now I'm wondering if I might move it
there and the server would go away. Comments, anyone?
Make a backup.
--Ken
No, I agree there hasn't been much work. I think the major sticking
issue for a 1.0.5 was that Dan was not happy with the new date parsing
code. The new code was a bit faster and actually compiled. The old
parser was some crufty code that was being munged with sed in order to
compile.
I would suggest Sourceforge not be used for a variety of reasons;
First being the fact that it is a sinking ship. If people feel a
Sourceforge-like site is really needed it would make more sense
to me to use savannah.gnu.org which is now open to non-GNU
projects.
What is wrong with mhost.com
Ken Hornstein wrote:
I don't see anything wrong with mhost, per se ... other than Dan (the
guy who was really driving nmh development) and Doug (the guy who hosts
the site) seem to be busy now. That makes it difficult to manage the
Hi, sorry to be late getting in on this, but you guys started
