Finally, the moment you've all been waiting for is here!
perlbug (http://rt.perl.org/rt3/) has been upgraded to the latest and
greatest version (RT 3.6).
Here are some changes you might notice:
- a new shiny look
- no more auth.perl.org, we now authenticate directly from bitcard.org
- a p
> I was going to suggest keeping an archive of this one outside the
> repository, but it's only 2 files, so I'll just keep a copy for
> myself. (I'd like to revive it at some point in PGE/TGE and the old
> implementation could be useful.)
Nothing is actually _deleted_ from SVN... it just gets har
> Given the recent explosion of svn commits in the synopses, and the fact that
> the versions of the synopses on the dev.perl.org/perl6 site are lagging a
> bit, would it make sense to add a link to the svn site to the
> Synopses page?
I'd rather not.
The ones on the dev site shouldn't have be
> > (If so, as a bit of background it's discussed at the bottom of #38217
> > on RT, and I tried to put together a patch in r11320 but I caused some
> > breakage so it's been backed out. I need to revive it)
>
> Thank you, Nick. How do I get a username and password for RT?
http://auth.perl.org/
> Applied in 11755, 11756, and 11758. (Ticket not closed; I don't have
> permission.)
You shouldn't say things like that. You have permission now.
-R (pulling an Audrey.)
Upgrade complete. You shouldn't notice anything different, except
some operations might be faster.
-R
At Tue, 21 Feb 2006 22:25:22 -0800,
Robert Spier wrote:
>
>
> FYI -
>
> At some point later this week, or maybe this weekend, I will be taking
> the perl.org Su
FYI -
At some point later this week, or maybe this weekend, I will be taking
the perl.org Subversion server down to move it to different hardware.
This most likely won't happen until after the imminent Parrot release.
>From an end user perspective, nothing should change. (Although we are
upgra
> Sigh. I wish it were that simple, or that funny.
>
> $ time wget http://cvs.perl.org/snapshots/parrot/parrot-latest.tar.gz
>
> real0m16.84s
> user0m0.09s
> sys 0m0.20s
>
> $ time svn co http://svn.perl.org/parrot/trunk parrot-trunk
>
> real 2:01:50.3
> user 1:02.0
> sys
> snapshots or releases. And, since a checkout takes about an hour (last
> time I checked) I tend to be too lazy to fetch one just to make a patch.
Only if you're checking out to a Commodore 64.
[EMAIL PROTECTED] /tmp$ time svn co http://svn.perl.org/parrot/trunk
parrot-trunk > /dev/null
re
> ... seems to be dead for about a day now, though I know commits are
> going through.
Fixed.
> BCCing webmaster at perl dot org, where this will hopefully open a
> ticket.
THANK YOU. This meant the message got seen much earlier than it
otherwise would, and because of the BCC, no collateral dam
> No, it isn't. =)
>
> The mail list strips out .t attachments (Robert? is this necessary?)
We don't strip .t We strip troff attachments. Really, it's a bad
mailer that is labeling the .t file a troff mime-type.
I've removed the troff types from the bad mime list.
-R
We've actually done a merge. It is complete. All committed changes
on the leo-ctx5 branch are now on trunk as of rev 9260. The leo-ctx5
branch was deleted as rev 9261.
If you have any checkouts of the leo-ctx5 branch, you will need to
switch them to trunk
cd parrot-checkout-of-leo-ctx5-br
> [1 ]
> On Sat, Jul 23, 2005 at 11:53:01AM -0700, Robert Spier wrote:
> > Thanks, applied.
> Thanks! However, the rendered form is still of an old revision:
> http://dev.perl.org/perl6/faq.html
It was still in my staging copy. It should be up now.
-R
Thanks, applied.
At Thu, 21 Jul 2005 01:39:42 +0800,
Autrijus Tang wrote:
>
> [1 ]
> Below is a patch to remove the first Q&A from:
> http://dev.perl.org/perl6/faq.html
Updated. (Sorry for the delay.)
-R
At Fri, 10 Jun 2005 20:18:38 +0100,
Roger Browne wrote:
>
> By the way, the website
> http://www.parrotcode.org/
> still refers to 0.2.0 as the latest version.
>
> Regards,
> Roger Browne
> The list server keeps eating my attached homework. Won't let me attach a
> .t file.
This is because your mailer is declaring it to be an
application/x-troff file.
> Leopold Toetsch wrote:
> > http://www.parrotcode.org/resources.html still has CVS and CVS
> > instructions mentioned. Please replace it with equivalent SVN hints.
>
> ... which are at http://www.parrotcode.org/source.html
Updated.
As always, patches for this kind of thing are welcome.
(You
> I noticed that the favicon.ico for http://www.parrotcode.org is a Camel.
> Can we have a Parrot for that, in order to do the many non-Perl Parrot
> based languages justice?
Good idea.
I've put one in place. If someone wants to make a nicer one, I won't
kick and scream too much.
-R
> Robert Spier wrote:
> >>>Doesn't work when svk is used to check out the copy. But in that case
> >>>svk list -R does.
> >>
> >>Hmm. Maybe this should be a commit action and not a test.
> > It was under CVS. I'm pretty sure everyone i
> The rsync off of cvs.perl.org::parrot-HEAD as suggested on parrotcode.org
> contains .svn directories. This doesn't seem right.
Fixed.
>
> Well, it always depends, how responds looks like:
>
> Committed revision 1234
>
> *
> ATT MAINFEST ERROR
> missing bla.bla ...
> *
This is very similar to what it did under CVS, although maybe not
quite as big.
Anyway, if this
> > Doesn't work when svk is used to check out the copy. But in that case
> > svk list -R does.
>
> Hmm. Maybe this should be a commit action and not a test.
It was under CVS. I'm pretty sure everyone ignored it there :)
-R
At Wed, 13 Apr 2005 02:07:05 -0400,
Roger Hale wrote:
>
> Robert Spier wrote:
> >>Could that be added as 4th line?
> > Good ideas, all of them. I've updated the page to add that, and to
> > switch to bz2.
> > -R
>
> Following Nicholas Clark:
&g
> Could that be added as 4th line?
Good ideas, all of them. I've updated the page to add that, and to
switch to bz2.
-R
> Fixed hopefully.
>
> $ find -name '*.t' | xargs svn ps svn:mime-type text/plain
> $ svn ci ...
Yes, that'll fix it.
Probably worth checking the mime-types for all the other files.
> and that dam.. check in runs for more then 10 minutes now
Ick. The network pipe is a little congested today,
> > The conversion is done.
> > http://www.parrotcode.org/source.html
> > Have fun!
> Sweet! Is there any particular reason why everyone should use https?
> Shouldn't http do for non-committers? Or am I nitpicking here?
Not really. http is fine for non-committers. But it was easier to
just doc
The conversion is done.
http://www.parrotcode.org/source.html
Have fun!
If there are issues, let me know, and I'll fix em when I get back.
Everyone who could commit before, should be able to commit now.
If you find things slow, it's because everyone is trying to check out
at once.
-R (gettin
> I've disabled all CVS write permissions as part of the transition.
> (Yes, this means wheels are turning.)
CVS will stay readable, but un-writable until tomorrow morning, when I
hope to announce SVN being up. The import is running while I sleep.
I caught I minor issue halfway into the previous
I've disabled all CVS write permissions as part of the transition.
(Yes, this means wheels are turning.)
> > Any questions?
> I assume current committer bits will be transitioned over too?
Actually, this would be a great time to get signed committer
agreements from everyone. But, since that probably isn't going to
happen, I'll just move over all the bits.
-R
Due to popular demand, among many other reasons, parrot will be
switching to Subversion at some point in the next few days.
I've placed a test conversion at https://svn.perl.org/parrot-test/
(It mirrors the state of the CVS repository as of this morning.)
Please take a look at it, and make sure
> It was on parrotcode or dev.perl.org at some point.
> Maybe that can be reused?
Our tinderbox.perl.org volunteer is working on it. We've been nudging
him, and he's got some cool stuff going on.
> The definitive answer is +< -- the pod document at
> http://dev.perl.org/perl6/synopsis/S03.html is out of date.
> This has been corrected in the perl6 svn repository for some time
> (http://svn.perl.org/perl6/doc/trunk/design/syn/S03.pod), but I don't
> know the magic for getting updates in the
From: O'Reilly Conferences <[EMAIL PROTECTED]>
Subject: OSCON Call For Proposals Now Open
Date: Thu, 20 Jan 2005 11:30:03 -0800
The Call for Proposals has just opened for the
7th Annual O'Reilly Open Source Convention
http://conferences.oreillynet.com/os2005/
OSCON is headed back to friendly, ec
> > Parrot is now listed on CIA
> > (insert-at-point (spook))
>
> Ooo. spook's phrasebook is strictly US-ASCII. That's totally CIA-compatible,
> isn't it?
Probably. But they're still after those computer criminals. And
folks who use laser pointers.
-R
Parrot is now listed on CIA
http://cia.navi.cx/stats/project/parrot
This will track all future commits, making them available as a RSS
feed, etc.
This slows down commits a little because of some work the script does
to try and merge requests. I can tweak a little if people start
noticing a del
Mr. Cowgill's computer did not send such a message to the list. (It's
not in the archive.) He sent it to you directly.
-R
At Wed, 22 Dec 2004 12:27:51 -0800 (PST),
Ovid wrote:
>
> OK, everyone send Mr. Cowgilll a polite message letting him know that,
> in the future, he needs to not send thes
> While I personally like the idea, I think it is unlikely given how
> much slower svn is on sizable repositories. Of course I have not
> tried it recently, so maybe that has changed...
> All that being said, I am in absolutely no position of authority about this...
This is, and always has been,
> I'd like to see:
...
http://rt.perl.org/rt3/NoAuth/parrot/Overview.html
> (In my opinion, the line-ending issue isn't a problem for Parrot in
> terms of this test--it's legitimate to expect that you can process a
> particular file, not matter what platform you happen to be on, and no
> matter if the file happens to have been created on another platform.)
Also, the pro
Is there anything that can be learned/reused from libjit?
http://www.southern-storm.com.au/libjit.html
-R
> Maybe there are some good links to Tinderbox or Bonsai or ViewCVS or they
> are only temporarily down, I don't know, but having non-functional
> references in documentation is not very good.
Tinderbox is temporarily down. Either Zach needs to fix it, or I need
to finish my replacement for it.
> - do not change viewcvs in glossary.doc to cvsweb, just correct the
> link
Please _do_ change all references to cvsweb to viewcvs. Unless there
is a compelling reason, we will continue to phase out use of cvsweb.
viewcvs is faster, cleaner, and has more features.
-R
[ We're down a handful this week... but not by much... thanks to Steve
Peters for going through some of the old ones and identifiying things
that can be closed. ]
Perl5 Bug Summary
http://rt.perl.org/rt3/NoAuth/perl5/Overview.html
Generated at Mon Sep 6 13:00:02 2004 GMT
This now lives at
http://svn.perl.org/parrot/cvs/ (use guest/guest)
http://svn.perl.org/viewcvs/parrot/cvs/trunk/
It is updated from CVS once an hour.
Have fun!
-R
At Sat, 7 Aug 2004 09:52:30 +0100,
Chia-liang Kao wrote:
>
> [1 ]
> Hi,
>
> I've just setup a Subversion mirror of the parrot
At Tue, 10 Aug 2004 22:05:34 -0400,
William Coleda wrote:
>
> [1 ]
> Attached find a patch to http://www.parrotcode.org/examples/index.html that:
>
> (0) depends on a patch I sent to the webmaster folks earlier adding back in the
> docs/* hierarchy (a small shim of .html files that just points
> Last year, I got different logs from Graham and Pair. Any other
> suggestions since they're apparently the same now? Mirror-owners I
> should talk to?
You could ask Graham for the search.cpan.org logs. Those are
potentially interesting.
-R
> I'll be redoing the Phalanx 100 this week. I'm hoping to get FTP logs
> from pair.com and from cpan.org. If anyone else has FTP logs they can
> submit to me, I'd love to have 'em.
$ host cpan.org
cpan.org has address 66.39.76.93
$ host cpan.pair.com
cpan.pair.com has address 66.39.76.93
> CVS ci rights for Jarkko would be fine,
Please send all requests like (and including) this one to cvs at
perl.org.
-R
> There's a directory platforms reappeared in parrot's CVS at the top level
> This breaks checkouts on any case insensitive file system, because CVS
> already knows about the file PLATFORMS
> We need the repository edited to expunge the directory platforms, don't we?
> Either that or the file PLATF
This might be useful... (thanks planetlisp!)
Chris Double
Wed Jun 30 17:22:09 2004
http://radio.weblogs.com/0102385/2004/07/01.html#a625
I came across a free portable arbitary precision integer and rational
arithmentic library called [1]IMath that looks useful. It is und
> Yeah, good point. pipeopen maybe? (Though then that gets confused with
> regular pipes) childproc? If it weren't so darned fundamental to the
> languages we care about I'd just throw the thing into the standard library
> and punt on it entirely...
It seems like an example of opcode bloat to me.
At Tue, 25 May 2004 10:36:24 -0400,
Aaron Sherman wrote:
>
> On Mon, May 24, 2004 at 09:48:45PM -0400, Uri Guttman wrote:
> >
> > is there a paypal PMC in the plans? will it be multi-accounted? will it
> > have built in auth support? what about rounding errors?
>
> In case it was not obvious, th
> ICU somehow manages (optionally?) to suffix all it its symbols with
> the version number, automagically (meaning, they don't look that way
> in the source or the headers). We should figure out how they are doing
> that, and see if we can use the same approach. I don't know if it's
> linker magic,
> Speaking about parrotbug, are the [EMAIL PROTECTED] addresses
> created? What do they currently do?
parrotbug@ sends to the tracker
status-{ok,nok}@ currently end up in mailboxes that nobody reads
-R
> clarification on some others - outgoing emails were being eaten by a
> grue for a while, but Robert says it's fixed now - I'll be sending out
To clarify. Only explicit CC's to the list were broken. All other
outbound mail was fine.
-R
>
> > b) Is it kosher/proper to update email references in it?
>
> Sure.
Disagreement. This makes it harder to find relevant email messages in
the archives.
-R
I've sent this off to the person who maintains that script.
In the future, the best place for reporting perl.org CVS related
problems is cvs at perl.org
-R
At Thu, 01 Apr 2004 17:10:28 +0200,
Leopold Toetsch wrote:
>
> $ sh ../allow\ temp\ vars\ as\ functions\:\ \$P0\(\).sh
> Access allo
> >about to cvs checkout parrot:
> >/home/perlcvs: no such repository
>
> Ah, that's finally gone away. The repository path is /cvs/publoc.
> What you're using's very old, though there was a temporary symlink in
> for a while.
It's been gone for months and months.
And you mean /cvs/public.
I can't replicate this.
At Tue, 16 Mar 2004 19:55:22 -0500,
Will Coleda wrote:
> bash-2.05a$ rm -f languages/tcl/lib/match_close.imc
> bash-2.05a$ cvs update languages/tcl/lib/match_close.imc
> cvs: rcs.c:4091: RCS_checkout: Assertion `options[0] == '-' &&
> options[1] == 'k'' failed.
> cvs [ser
> http://www.parrotcode.org/ is not responding to http or ping.
Yes. We knew. All happy now.
-R
> But what should those addresses do when receiving a message?
> - parrotbug: should open a RT ticket?
Yes. This is the new equivalent of bugs-parrot at rt.perl.org.
Use of that address should be phased out in favor of the new one.
> - status-ok: ?
> - status-nok: should open a RT ticket
At Thu, 11 Mar 2004 19:00:18 +0100,
Jens Rieks wrote:
>
> [1 ]
> Hi,
>
> Am I the only one who receives this annoying message each time I send an .tgz
> attachment to the list?
>
You're the only one who has complained.
I'll unsubscribe the offender.
-R
> >
> > That depends if google properly supports "moderated" newsgroups.
>
> Sounds like they don't ...
>
> In any case we don't currently support posting via nntp through
> anything but nntp.perl.org.
Actually, I think we need to get the uunet.uu.net folks to setup some
entries for us. But I
That depends if google properly supports "moderated" newsgroups.
Without knowing what they're doing, it's hard to guess what's going on
or where your message got eaten.
Your message _shouldn't_ show up on google unless it comes through a
proper newsfeed. This might mean that google's upstream (
> >
> > "within reason". Thats where we're way off right now.
>
> Let's keep a bit of perspective here. The non-Parrot:: contents of lib
> accounts for only 4.6% of the non-ICU content (and only 1.5% if you
> count ICU in the total size). It's difficult to see that as
> unreasonable, or as "bl
> But once we start expecting people in the real world to compile this thing
> on their boxes in order to install perl, it would be extremely foolish to
> make them manually download and install perl6 + parrot + icu + perl5 +
> cpan modules 1 through 10, all from different sources.
Try building
> > This kind of bug shouldn't happen if people actually read the messages
> > the cvs commit spits out.
> >
> > It will tell you that the manifest check it runs on every commit
> > fails. Please don't ignore it.
> Maybe a silly proposal, but nevertheless:
> Why are files not added to MANIFEST aut
> The determinism seems perhaps worth the bloat. It's quite localize
> bloat after all.
I disagree.
We _want_ a heterogeneous environment -- a homogeneous environment
doesn't exist in the real world -- most of your concerns were with
tracking down the issues. Since we have parrotbug now (or rea
> The mails are indeed sent to parrotbug, parrotstatus-ok and
> parrotstatus-nok (at parrotcode.org) for resp. bug reports, ok reports
> or nok reports. And since I don't think those addresses are set
> up...
Not yet. I'm nudging Ask regularly about this.
-R
> I agree. That's why I'd like to see TAI be the default "seconds
> since some epoch".
It seems like we want the "default" to be the simplest and fastest one
we can support.
If someone wants something different, they can do the moral equivalent
of:
use Time::TAI;
or
use Time::UTC;
or
> > No. Sorry, definitely not. Parrot's config isn't going to install
> > perl modules off the 'net any more than it's going to run apt-get on
> > systems that support it. We either provide it or do without.
>
> What about ICU. There is already a new version pending (again).
Since we haven't act
> >I'd like to remove non-modified, non-parrot Perl modules from lib
> >and install them via CPAN.pm.
>
> No. Sorry, definitely not. Parrot's config isn't going to install
> perl modules off the 'net any more than it's going to run apt-get on
> systems that support it. We either provide it or
> In a similar(?) vein,
>
> www.parrotcode.org/faq/ currently has a number of broken links,
> including "apocalypses", "PDD6", and "Java bytecode to Parrot bytecode".
This is because the links are funny.
The best way to get proper links is to do something like:
Lhttp://www.cnn.com>
That's no
ely:
>
> http://rt.perl.org/rt3/Ticket/Display.html?id=27304
>
> On Wednesday, March 3, 2004, at 01:15 AM, Robert Spier wrote:
>
> >
> > As promised.
> >
> > The "new" site is now live.
> >
> > -R
> >
> --
> Will "Coke" Coledawill at coleda
> dot com
> Bored now!
/me runs and hides.
Applied!
(I should just give you access.)
-R
>
> On Wednesday, March 3, 2004, at 06:39 PM, Robert Spier wrote:
>
> >> ... and then I got bored.
> >
> > ;)
> >
> > Thanks, all those changes applied.
> parrotbug is missing in MANIFEST which causes a make test error.
This kind of bug shouldn't happen if people actually read the messages
the cvs commit spits out.
It will tell you that the manifest check it runs on every commit
fails. Please don't ignore it.
-R
> > 26898, 26904, 26927, 26939, 26941, 26945, 26953,
> > 26956, 26964, 26976, 27097, 27098, 27143, 27150 -- spam
> already reported these and they are to be "cleaned out soon" ;)
> (there have been a few spam slippages lately)
Killed.
I still need to go back and do the monthly spam filter upda
> ... and then I got bored.
;)
Thanks, all those changes applied.
-R
As promised.
The "new" site is now live.
-R
>
> This is on my list for tonight. I've got something all ready to go
> but have been busy with a $NEW_JOB.
>
> -R
>
> At Tue, 2 Mar 2004 00:44:02 -0500,
> Mitchell N Charity wrote:
> >
> > The parrot homepage
> > http://www.parrotcode.org/
This is on my list for tonight. I've got something all ready to go
but have been busy with a $NEW_JOB.
-R
At Tue, 2 Mar 2004 00:44:02 -0500,
Mitchell N Charity wrote:
>
> The parrot homepage
> http://www.parrotcode.org/
> currently says
> Periodic releases will appear on CPAN; the current
> - it only accepts -ok / -nok flags (no *real* bug reports to be
>edited)
This may or may not be good. We need a new processing system (for
perl5 too) to deal with the -ok reports.
> - I'm not sure about the reporting address (Robert, I need your advice
> on this one)
I suppose, it sho
> Given that the new webpage won't be replacing the old webpage in time
> for this upcoming release...
>
> I suggest we make a few simple modifications to the _existing
> website_.
I'm not going to make any more changes to the existing website, but
since you asked nicely, I made these.
> Also, a
> I brought this up several months ago and was told that a new webpage was
> in the works. Where in the works is it? Does it have an expected time
> to leave the works? I agree with Mitchell that it is important to
> maintain a public face (lest we send the wrong impression).
It will be leav
> >>Better it get fixed in CVS. There could be more errors of this kind.
> > Confused. What would you like me to do?
>
> Please purge the platforms directory on the server. It collides with the
> PLATFORMS file on these poor pseudo-OS, that have case-insensitive
> filenames. (There could also s
> > After a bit of self-education on the CVS FAQ, I've come to the
> > conclusion that "renaming" (delete/add) PLATFORMS to PLATFORMS.txt is
> > the best way to solve this.
>
> Better it get fixed in CVS. There could be more errors of this kind.
Confused. What would you like me to do?
Also.
cv
> Suppose I could make a few changes to Pod-Simple, then our problem
> would be solved.
Pod::Simple is relatively easy to subclass. And Sean is pretty
receptive to changes.
> never have occurred to me to shove all of that in CVS. It always
> surprised me a that ICU was there, rather than just
> Either merge them or close 26056 as wontfix or equivalent (sorry, I'm
> a Bugzilla feak :). The first patch has conflicts with current source,
> which is why I freaked out when it didn't show up pronto.
Done. Sorry for the trouble.
-R
I think I've tracked this down, mostly.
The patch was rejected from the mailing list because it was
too big. (Several hundred k.)
You can find it in RT as
26056: [PATCH] Unify PMC accessor macros 2
26057: [PATCH] Unified PMC/PObj accessors phase 2
(26057 is one that points to a URL. Gordon,
> Did it have an executable attachment? :-)
If anyone wants some MyDoom, I've got over a gigabyte (from the past
19 or so hours) absorbed by the perl.org servers I'd be glad to share
with you. I can arrange for them to be emailed one at a time, or all
at once.
-R
At Thu, 5 Feb 2004 11:25:22 -0500,
Gordon Henriksen wrote:
>
> [1 ]
> I've submitted a patch to bugs-parrot, and it didn't seem to get posted
> to RT or otherwise handled. Anyone know where it might've gone?
I'm the one who would know. Please email me off-list with the
message-id, subject, from
> I can possibly help it, so it's ok by me to delete lib/Pod, if that's
> the consensus.
I'm not sure what the consensus is. But we should probably come to one.
-R
> I've added the Perl modules for the docs tools to lib/Parrot/IO and
> lib/Parrot/Docs. I've also added Pod-Simple (2.05) and Pod-Escapes
> (1.03) which they use.
I probably blinked.. but why are we including CPAN modules that we are
not likely to change into the parrot repository?
-R
Melvin,
We're having some issues at perl.org due to the worm/virus/bounce
stuff. Slow delivery is just something we're going to have to
deal with for a few more days... but bounces I don't like.
If your legitamite email is getting bounced by the perl.org
(develooper.com) ser
> Right, good point. In that case, if we could give our intrepid and
> possibly slightly mad volunteers Dave Pippenger (dpippen) and
> Stephane Peiry (stephane) privs on the bug and todo queue for parrot,
> that'd be great -- we can start handing out todo tickets to folks for
> doing.
done-o.
> Is there any way to get RT to close tickets (or change their status)
> entirely via e-mail? That'd make this a lot easier if we could throw
> a:
> RT-Status: Closed
> or something like it in the reply to a bug report that notes the bug
> has been fixed.
I could implement this, but there are a
> Thanks for taking this on.
No problemo.
> > 22558: Another Hack at constant propogation
> Aplied or Fixed and then applied (I forget which)
>
> > 24847: [patch] simplify register stacks (remove code duplication)
> Reject (resubmitted late as a different patch which was applied)
Noted.
(FYI,
Here are 177 currently outstanding parrot issues in the RT system.
You can see more detail on them by going to:
http://rt.perl.org/
clicking on guest access, and then typing the number into the upper
right hand corner box.
what we're mostly looking for are issues that can already be marked a
> In the mean time, if anyone else has todo list items, send them
> (*ONE* per e-mail!) to bugs-parrot at bugs6.perl.org to get 'em in
> the queue and we'll start sorting them out from there. If we're lucky
> and have sufficient web luck we might even get 'em into a
> web-accessible TODO list (
> I didn't realize there was moderation. (How was spam getting through?)
Spam was getting through because when I upgraded RT, I didn't
re-insert some of my envelope massaging magic, which meant that spam
was looking as if it was coming from a "valid" address, when it really
wasn't.
Once I re-inse
1 - 100 of 256 matches
Mail list logo
