Do we have any idea yet when this will be done? It would be nice to find
the patches.
I am especially looking for the one that allows html footers to use it to solve
the AOL problem that no one either knows how or volunteered to write a
script to gather the redacted ARF addresses from the mail log. I remember
there once was a mod to make the headers and footers html, and wanted to
see if that would work.
Date sent: Mon, 8 Sep 2008 07:47:32 -0700
From: Mark Sapiro <[EMAIL PROTECTED]>
To: "Stephen J. Turnbull" <[EMAIL PROTECTED]>,
Richard Barrett <[EMAIL PROTECTED]>
Organization: Not Very Much
Copies to: mailman-users@python.org
Subject: Re: [Mailman-Users] Availability of patches on
Launchpad
> Stephen J. Turnbull wrote:
>
> >Richard Barrett writes:
> >
> > > I guess it is not intended that the old approach with sourceforge of
> > > putting enhancements into the tracker with patch files attached,
> > > should be followed with Launchpad. I expect someone is going to tell
> > > me I should create my own branches of Mailman on Launchpad for each
> > > of my enhancement and publish what were patch file contents in that
> > > way.
> >
> >I imagine that is the "preferred method" for *future* patches, but
> >since Canonical is after World Domination Now (or at least a market
> >share that requires units greater than nano-percents to measure), they
> >had better not lose history this way. I advise you to assume that
> >this is just a bug (albeit a rather distressing one) that will be
> >fixed in due time, until somebody says otherwise.
>
>
> Stephen is correct that this is a serious bug in the migration process.
> It was not intended that anything would be culled or lost in this
> process.
>
> It appears that the same problem existed in the "demo" that was
> announced last month
> (<http://mail.python.org/pipermail/mailman-developers/2008-August/020345.html>
> and
> <http://mail.python.org/pipermail/mailman-users/2008-August/063021.html>),
> but it wasn't caught.
>
> Nothing is permanently lost as the SourceForge trackers still exist.
> They just aren't currently accessible by other than project members.
>
> Unfortunately, Barry may not yet be aware of this as at least
> yesterday, the primary MX for list.org was not working, but I'm
> confident that this problem will be fixed.
>
> --
> Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
> San Francisco Bay Area, California better use your sense - B. Dylan
>
> ------------------------------------------------------
> Mailman-Users mailing list
> Mailman-Users@python.org
> http://mail.python.org/mailman/listinfo/mailman-users
> Mailman FAQ: http://wiki.list.org/x/AgA3
> Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
> Unsubscribe:
> http://mail.python.org/mailman/options/mailman-users/lists%40viplist.us
>
> Security Policy: http://wiki.list.org/x/QIA9
Thanks.
Lloyd F. Tennison
[EMAIL PROTECTED]
No trees were harmed in the transmission of this message.
However, a rather large number of electrons were temporarily
inconvenienced.
------------------------------------------------------
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
