* On 2007.05.02, in [EMAIL PROTECTED],
* Jeff Kunzelman (DHL) [EMAIL PROTECTED] wrote:
Is there a way that I can use the withlist command to change the display
name of a mailman list?
You can, but you must write valid python code that manipulates
properties of the list object.
Hi,
On Thu, May 03, 2007 at 11:16:57AM -0400, Barry Warsaw wrote:
snip
Alioth
See http://wiki.debian.org/Alioth and
https://alioth.debian.org/projects/siteadmin/ for information about this
service.
is for Debian only, right?
Any free software project where a Debian Developer is involved
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 3, 2007, at 11:50 AM, Jon Scott Stevens wrote:
Since I haven't seen anyone else mention this... there is also:
http://en.wikipedia.org/wiki/SVK
I say stick with Subversion/SVK:
#1. *everyone* knows how to use it and almost all OSS
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 3, 2007, at 12:57 PM, Stephen J. Turnbull wrote:
Barry Warsaw writes:
Your point about interoperability is an important one, and definitely
a factor in the decision. I think the risk is mitigated by tools
like Tailor,
Tailor is great,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 3, 2007, at 2:06 PM, Mads Kiilerich wrote:
Barry Warsaw wrote, On 05/03/2007 05:16 PM:
Alioth is for Debian only, right? Would they host Mercurial branches
for other FLOSS software like Mailman? If we go with Mercurial,
we'll need
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 3, 2007, at 9:45 PM, A.M. Kuchling wrote:
On Thu, May 03, 2007 at 08:50:16AM -0700, Jon Scott Stevens wrote:
http://en.wikipedia.org/wiki/SVK
What about SVK's speed, though?
There was discussion of providing a DVCS mirror of the Python
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 3, 2007, at 10:42 PM, Ethan Fremen wrote:
Barry Warsaw wrote:
Of course, I think it /will/ make our lives harder in some ways. As
we've seen, folks like cPanel have their own forks that they modify,
and then their users come looking to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 4, 2007, at 8:02 AM, Joost van Baal wrote:
Hi,
On Thu, May 03, 2007 at 11:16:57AM -0400, Barry Warsaw wrote:
snip
Alioth
See http://wiki.debian.org/Alioth and
https://alioth.debian.org/projects/siteadmin/ for information about
this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On the Mercurial front, last night I tried to use yasvn2hg to convert
the Mailman repository to hg. The conversion failed however:
Error: could not classify changeset 102
I haven't had time to try some of the other conversion scripts.
I'd bet
Barry Warsaw writes:
So my take away from this is that while a conversion would be /
possible/ it's not completely seamless or automatic. If we choose
wrong, we'll suffer some pain, but we'll recover. ;) Would you say
that's accurate? I could live with that.
I really doubt we'd
Barry Warsaw writes:
Is anybody interested in trying to complete the Mercurial
conversion? I can make a bz2-tarball of the svn repository available
if you want to give it a shot. It's about 87MB.
I'll take svn2hg via Tailor, since that's what I'm using anyway for
XEmacs.
I remember a number of threads about backscatter prevention, but I
don't remember the result. Perusing the archives isn't much more
enlightening. Where are we on this?
In particular, other than removing all but one of the aliases, have
we made it easier for people to run a backscatter
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 4, 2007, at 2:21 PM, Stephen J. Turnbull wrote:
Barry Warsaw writes:
Is anybody interested in trying to complete the Mercurial
conversion? I can make a bz2-tarball of the svn repository available
if you want to give it a shot. It's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 4, 2007, at 3:57 PM, Stephen J. Turnbull wrote:
That's right. In my integration workspace maintained under git, I
basically branch for *every* commit back to the XEmacs CVS, and delete
the branch when I see the commit notice. In my
Barry Warsaw wrote:
I propose that no matter which way we go (Mercurial, Bazaar or
something else), we convert only the trunk. Let's leave the stable
2.1 branch on SF under Subversion, but do all new development in the
dvcs. It will be a bit more painful to commit fixes across both
Barry Warsaw writes:
I propose that no matter which way we go (Mercurial, Bazaar or
something else), we convert only the trunk. Let's leave the stable
2.1 branch on SF under Subversion, but do all new development in the
dvcs.
Why not do both? That is, if Tailor does its thing
16 matches
Mail list logo
