Re: [Nmh-workers] nmh current development

2005-05-10 Thread K Suominen
On 5/10/05, Oliver Kiddle <[EMAIL PROTECTED]> wrote: > Josh Bressers wrote: > > I must admit that I've not paid a lot of attention to this list in the > > past, so I'm hoping someone can fill me in on some details here. I > > submitted a few somewhat lame patches on savannah a bit over a week ago.

Re: [Nmh-workers] nmh current development

2005-05-10 Thread Ken Hornstein
> > though. I'll even stop whining about putting autoconf-generated in CVS > > (I'll still think that it's a huge mistake, I just won't say anything > > about it :-) ). > >do you think it's a mistake even if they're commited under >non-standard names? i agree that they probably shouldn't be >comm

Re: [Nmh-workers] nmh current development

2005-05-10 Thread Josh Bressers
> > though. I'll even stop whining about putting autoconf-generated in CVS > > (I'll still think that it's a huge mistake, I just won't say anything > > about it :-) ). > > do you think it's a mistake even if they're commited under > non-standard names? i agree that they probably shouldn't be

Re: [Nmh-workers] outstanding patches

2005-05-10 Thread Arun Bhalla
Paul Fox writes: > > > > Patch 758 > this is "Set Preferred Types When Displaying multipart/alternative" This is one patch (of many) I'd love to see in an nmh release. Seeing the text/html part instead of the text/plain part has driven me crazy for years! In the meantime I'll have to build n

Re: [Nmh-workers] nmh current development

2005-05-10 Thread Paul Fox
> though. I'll even stop whining about putting autoconf-generated in CVS > (I'll still think that it's a huge mistake, I just won't say anything > about it :-) ). do you think it's a mistake even if they're commited under non-standard names? i agree that they probably shouldn't be committed u

Re: [Nmh-workers] nmh current development

2005-05-10 Thread Ken Hornstein
>Jerry, I don't think that this is quite right. I'm willing to take over >releases if need be. Any time that I've tried to push on this in the >past the current maintainer has gotten offended and promised to eventually >do something. We did have a change in maintainer a few years ago, and I >get

Re: [Nmh-workers] nmh current development

2005-05-10 Thread Ken Hornstein
>I must admit that I've not paid a lot of attention to this list in the >past, so I'm hoping someone can fill me in on some details here. I >submitted a few somewhat lame patches on savannah a bit over a week ago. >My purpose in doing this was to test the waters a bit to see if development >is as

Re: [Nmh-workers] outstanding patches

2005-05-10 Thread Paul Fox
> There are quite a few patches on savannah or the mailing lists which > have never been applied. Given that people went to the effort of > creating these it is silly for them to go to waste. Over the past year > or so, installing nmh for me has meant checking the source out of CVS, > applying

[Nmh-workers] outstanding patches

2005-05-10 Thread Oliver Kiddle
There are quite a few patches on savannah or the mailing lists which have never been applied. Given that people went to the effort of creating these it is silly for them to go to waste. Over the past year or so, installing nmh for me has meant checking the source out of CVS, applying a couple of pa

Re: [Nmh-workers] nmh current development

2005-05-10 Thread Oliver Kiddle
Josh Bressers wrote: > I must admit that I've not paid a lot of attention to this list in the > past, so I'm hoping someone can fill me in on some details here. I > submitted a few somewhat lame patches on savannah a bit over a week ago. > My purpose in doing this was to test the waters a bit to s