I wrote a long screed, full of piss and vinegar. But on reflection,
clearly nobody is reading what I wrote earlier, so let's try pithy and
dry. It's still long. :-(
Chip Davis writes:
> OK guys, what's really going on here?
I don't know. I can tell you I'm done with Jim. You'll have to ask
Dennis Putnam writes:
> Since Centos 7 is way behind on mailman rpm (2.1.15 is the only
> available rpm) and mailman is currently at 2.1.34 I need to do a manual
> update. While I know how to install software, I am concerned that just
> doing a manual install from the tarball will mess up curr
I'm done, Jim.
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Secur
Since Centos 7 is way behind on mailman rpm (2.1.15 is the only
available rpm) and mailman is currently at 2.1.34 I need to do a manual
update. While I know how to install software, I am concerned that just
doing a manual install from the tarball will mess up current settings,
lists and members. Do
On 8/28/20 11:47 PM, Carl Zwanzig wrote:
>
> If the existing
> gnu-mailman team doesn't want new members working on old code, and
> that's the way it sounds, just say so and give the blessing for a code
> fork.
We never said that. We only asked that these potential new members
actually ask to jo
On Fri, 2020-08-28 at 23:47 -0700, Carl Zwanzig wrote:
>
> Or... it's pretty likely that MM2 maintenance, and maybe improvements, will
> continue in some fashion. The question is whether that's under the auspices
> of the gnu-mailman project or in a fork. If the existing gnu-mailman team
> does
