Just some brief comments... $0.02 or some such. :)
-R
Quoting Dave Mitchell <[EMAIL PROTECTED]>:
> =item *
>
> "K&R" style for indenting control constructs: ie the closing C<}>
> should
> line up with the opening C etc.
You should provide a short example here - K&R has lots of nasties, you
>>How about something a little more explicit than XXX, like TODO or FIXME?
> Some syntax-highlighting editors highlight "XXX". Let's use that feature.
Which ones? emacs doesn't seem to do it by default.
> And how can you get more explicit than XXX, anyway?
Funny, but I still think TODO or
Yes-
People just need to agree to send all patches to RT first so that
they can be tagged in their subject line, so discussion gets
tracked. For now, RT needs to be CC'ed on followups - soon it
will just "listen".
When Simon/Dan/$PATCHER applies/rejects a patch, they can t
Quoting Dan Sugalski <[EMAIL PROTECTED]>:
> Hmmm. I think we need a reorg of the source directories, then. I'll get
>
> with Simon and coordinate doing this. (It's going to make CVS *so*
> happy... :)
It's often easier to do this by moving the RCS files inside the CVS respository
directly - it's
I think there's an extra / in the cvs add line in the loop.
Gibbs Tanton - tgibbs writes:
>I don't think anyone objects to this...I vote go ahead and move the .h files
>and modify Makefile.in according to Brent's email.
>
>Tanton
>
>$ cvs -q upd -AdP
>$ mkdir -p include/parrot
>$
Gibbs Tanton - tgibbs writes:
>Ok, here is the rule based makefile...
Thanks
Looks good (and works for me.)
I suggest the following patch on top of Gibbs' patch, to seperate form
and function of CC and CFLAGS. (Also, the "standard" (fwiw) is
CFLAGS, not C_FLAGS)
-R
--- Makefile.in.1
Dan,
Could you explain again why you don't want char* anywhere, and prefer void*?
You answered this on language-dev, but went off on what seemed to be a tangent
about encodings.
Some ramblings of my own that may be confusing me, are:
char* doesn't necessarily mean "a string".
would t
Quoting Dan Sugalski <[EMAIL PROTECTED]>:
> > Could you explain again why you don't want char* anywhere, and
> prefer
> > void*?
>
> Because for character data we're not sure char * is right. (Might be
> wchar_t, __int16, __int32, or something else) It's also to shake off the
>
> "Oh, it's
>> Ant is different. Instead of a model where it is extended with shell based
>commands, it is
>> extended using Java classes. Instead of writing shell commands, the
>configuration files
>> are XML based calling out a target tree where various tasks get executed.
>Each task is run
>> by an object
On Tue, 2001-10-23 at 20:52, Russ Allbery wrote:
> Dan Sugalski <[EMAIL PROTECTED]> writes:
>
> > Once we build miniparrot, then *everything* can be done in perl. Having
> > hacked auto* stuff, I think that'd be a good thing. (autoconf and
> > friends are unmitigated evil hacks--people just don't
> So I know for the first-stage rollout, does Apache's module system support
> Apache managing filehandles and modules calling apache's I/O routines, or
> does it just do weird magic with I/O on normal filehandles?
I'm pretty sure that for a simple implementation, we only need to worry
about "
On Sun, Nov 11, 2001 at 07:38:28PM -0500, Ken Fox wrote:
| I'm finishing up my design for lexicals and I'd like to
| provide a graphical presentation. PDF is probably the
| best choice for viewing, but what is the best format for
| the source? I've been using "dia", but maybe something
Dia is ve
>I was wondering about *editing* them. IMHO all the data
>structures in Parrot must be documented as beautifully as
>PerlGuts Illustrated. Parrot is evolving quickly though
>and needs documentation that is easy to update.
Yes. Definitely. I think PerlGuts used GraphViz.
>"dia" is probably a wo
The tinderbox is showing some unhappyness:
http://tinderbox.perl.org/tinderbox/showbuilds.cgi?tree=parrot
I think some things may just need to be kicked.
-R
| I'm OK requiring a C compiler and a build tool for a platform. It's a C
| compiler and perl 5 that I don't want to require. (Rather nasty
| bootstrapping issues there... :)
This makes things a lot harder. Suddenly we're
re-implementing make. (in C)
Speaking of re-implementing make, I just
On Wed, 2001-11-28 at 18:22, [EMAIL PROTECTED] wrote:
> hey,
>
> I'm trying to set up tinderbox here for parrot on two systems (sun5.6 and omvs
> (open edition os/390))
>
> Unfortunately, I can't see to port 2401 in the outside world because of
> firewall (to do the continuous checkout from cvs
With a little bit of substitution magic, a serious abuse of dynamic
linking, a count or two of using static data improperly, mod_parrot
can now have scripts which output to the users' web browser.
I think they're coming to take me away... put me in a little blue
room for a while...
If you want
| patches integrated in soon, and a longer-term solution (i.e. a perl make)
| should be ready not too long after that.
bool query {
Dan, you've been unclear. Is a perl5 based make system
where you want to be today?
}
-R
[amk - Fri Dec 14 20:42:39 2001]:
> Running "make distclean" with a post-0.0.3 snapshot of the CVS tree
> deletes all the files in CVS/ subdirectories, making further updating of
> the tree impossible.
This patch makes 'make distclean' not blow away CVS files.
Is this the answer, or should we c
On Sun, Dec 30, 2001 at 10:11:38AM -0500, Gregor N. Purdy wrote:
> Bryan --
>
> > Mixed modes for *.pl scripts in the main directory. Should all probably be
> > 0644.
>
> Changing them directly in the repository should help.
$ chmod 0644 *.pl,v
Done.
-R
> > An updated TODO list is needed. As is maybe a reminder on bugs.perl.org.
bugs6.perl.org
> The things that I want to happen for 0.0.4 are not sexy. They are
I've added the 0.0.4 goals to
http://www.parrotcode.org/todo
-R
At Simon's request, I will be moving things around in the CVS
repository tonight between 7 and 11 PM PST (GMT+8).
I'll disable commit access, and will send out a note when I'm done,
with a summary of the changes. If you have files checked out and they
are being worked on, you will need to eithe
The following things have changed:
- Renamed include/parrot/register_funcs.h to regfuncs.h
- Renamed languages/miniperl/miniperlc to mpc
- Moved t/op/pmc* to t/op/pmc/
- Moved Parrot/* to lib/Parrot/
- Moved Test/* to lib/Test/
Revision history has been preserved in the following manner:
- th
On Fri, 2002-01-25 at 09:07, Melvin Smith wrote:
>
> >1.> There is no link to the FAQ on the Perl6 page (that I could find
> anyway).
> > (http://www.panix.com/~ziggy/parrot.html - I think this it)
>
> This really should be stored or linked in the Perl6 Parrot area.
>
The new location is h
> >I could also replace some "perl foo" calls with "./foo" if someone
> >wanted to set the executable flag in CVS on assemble.pl, optimize.pl,
> >etc.
Done. (For all the .pl files in the root directory.)
You'll need to delete them and let CVS recreate them (cvs update) for
the change to take e
Dan Sugalski writes:
>At 1:08 PM -0800 2/3/02, Robert Spier wrote:
>> > >I could also replace some "perl foo" calls with "./foo" if someone
>>> >wanted to set the executable flag in CVS on assemble.pl, optimize.pl,
>>> >etc.
>>
>>In general, try a cvs update -P, which should eliminate empty
>>directories.
>
>Thanks. A clean CVS checkout was catching them and causing problems
>for me. Pity CVS doesn't let you delete directories remotely.
You might need a checkout -P too.
Pity CVS doesn't version directories. ;)
-R
> make quicktest could screw up if:
> - you ctrl-c it, or make test (although I haven't had problems with that
> yet) during the compilation process at just the right time
> - you do anything to invalidate existing .pbc files, such as rearranging
> ops. not sure what else could trigger this.
>
>
>This satisfactory? (I didn't mention it in the README because that's
>supposed to be simpler instructions sans caveats, imo)
Looks good to me.
Thanks, Applied!
-R
> Keep track of global (or interpreter local) scope with a macro
> upon entry.
I shudder every time someone says "macro" on p6i.
perl5 has several thousand macros defined. (grep for ^#define) (over
8000 if you include all the embedding macros. it's down to ~4000 if you
cut out embedding, co
Melvin Smith wrote:
> At 10:30 PM 4/8/2002 -0700, Robert Spier wrote:
>>> Keep track of global (or interpreter local) scope with a macro
>>> upon entry.
>> I shudder every time someone says "macro" on p6i.
>> perl5 has several thousand macros def
Looks like we've got a slew of gcc3 issues (which don't show up on the
tinderboxes, cause nobody's running a gcc3 box.)
rspier@bear ~/projects/parrot$ make test
perl t/harness
t/op/basic..ok
t/op/bitwiseok
t/op/debuginfo..ok
t/op/hacks..ok
t/op/ifunless...ok
t
Dan Sugalski wrote:
> At 11:47 PM -0700 4/13/02, Robert Spier wrote:
>> Looks like we've got a slew of gcc3 issues (which don't show up on the
>> tinderboxes, cause nobody's running a gcc3 box.)
> What sub-version of GCC 3?
3.0.4
(running on a relatively stoc
>>> What sub-version of GCC 3?
>> 3.0.4
>
>
> Damn. Do the failing tests segfault?
I didn't look that closely. Some of them definitely are spitting out
wrong data. (Very odd.)
I didn't notice any Segmentation Fault warnings in the output though, so
I'd guess no, unless it's being trapped b
>Without knowing too much about it, I still have to wonder what is
>wrong with cons? I thought it was a fully functional all-perl make
>replacement.
One reason not to use cons is that we will have to port it to
parrot/perl6 in order to become self hosting, another, is that it
may not meet all of
Dear p6i members...
Sadly, this piece of spam snuck through our perl.org spam filters
and got into the bugtracker which dutifully passed it on to to the
mailing list.
Please do not report this to us, or pass it to spamcop. Because
the full headers aren't in what you recieve
Dan Sugalski writes:
>Okay, the first draft of PDD3, calling conventions, is in. Sync up,
>rip in, and let fly... :)
Also available on the website, http://dev.perl.org/perl6/pdd/, updated
daily.
-R
MIPSPro is unhappy:
http://tinderbox.perl.org/tinderbox/showlog.cgi?log=parrot/1020037080.95964.gz
--
Steve Fink (via RT) writes:
>I don't know how easy it is to find this since it only went to the
>bugs address, so here's a repeat followup patch to the sized resource
>pool patch (I accidentally left this out):
New bugs sent to the bugs address are forwarded to the list.
Anything on the list wit
>Is there a 'Superseded' or 'Obsolete' state? It's nice to be able to
>tell the difference between a patch that was considered a bad idea or
>just succumbed to bit rot, and one that was replaced with an
>alternative implementation before making it in.
There is now.
:)
-R
When submitting patches through the bugtracker, please do not CC the
list as well. (This leads to duplicate tickets, because people reply
to the non-managed version and CC the tracker etc.)
the bugtracker (http://bugs6.perl.org) automagically sends new tickets
to the list.
If you have any prob
Steve Fink writes:
>What about followups? The way I've settled on doing things is to send
>only to the bugs address initially, but then reply to both bugs and
>the list for any followup correspondence. I know that replying to just
>the bugs address isn't enough because it only forwards the initial
New!
See the list of open/patches in the bugtracker.
http://www.parrotcode.org/openpatches
(Next step is to have tickets where $subject =~ /\[patch\]/i
automatically be marked as patches -- so I don't have to do it by
hand.)
-R
I've got two things to look at now.
Taking/Closing tickets requires me to grant you special access (which
I will do if you ask.)
I'm going away for the weekend, so I'll take a look at these two
issues on monday or tuesday.
-R
will coleda writes:
>Which reminds me:
>
>I have an account, but
>#define PARROT_str_local(d)\
> STRING * d = NULL; \
> frame frame_##d;\
> int dummy_##d = ( \
> (frame_##d.ptr = &d), \
> (frame_##d.next = stack_top), \
> (stack_top = &frame_##d), \
>
>What are the debugging issues you mention? Note that this macro will
>never fail: there is no pointer deferencing, no memory allocation, ...
Never is a bad word to use for anything more complicated than x=1+2.
(Which will hopefully get constant folded and optimized away anyway.)
It is impossib
Apologies for this test, I'm tracking down reports that attachements
aren't getting through the list and getting to the bugtracker.
-R
Apologies again for this test, I'm tracking down reports that
attachements aren't getting through the list and getting to the
bugtracker.
It helps if I actually attach the temp file.
temp
Description: Binary data
>Has the CVSROOT changed ?
Last November. :)
>>cvs checkout parrot
>
>/home/perlcvs: no such repository
>cvs checkout: authorization failed: server cvs.perl.org rejected access to
>/home/perlcvs for user anonymous
Use /cvs/public
-R
Thanks, Applied.
Clinton A. Pierce writes:
>Fixes the problem where the toplevel makefile can't descend into lib/Parrot
>to do the build necessary for PackFile and friends. Also I think the
>single cd .. may potentially be a bug for other platforms as well.
>
>Apply this and re-run Configure.
--- start of forwarded message ---
Date: 7 Jun 2002 21:36:26 -
From: Joe Yates (via RT) <[EMAIL PROTECTED]>
Cc: recipient list not shown: ;
Subject: Re: [netlabs #590] Ticket Resolved
Message-Id:
Dear Daniel,
I hope I'm not being a pain. The response to my report was that "This'll
I've updated http://www.parrotcode.org/todo with the latest info from
Dan.
Dan Sugalski writes:
>Here's the list 'o stuff I'd like to get done for August:
>
>*) Multiple interpreters with inter-interpreter calling done right
>*) Threads with multiple independent interpreters
>*) Method calls
>*
There's enough words and definitions going by that not everyone
understands that it's time for us to have a glossary.
I'm willing to do the administrative work of maintaining it, if others
send me entries.
So... if there are words you think should be in the parrot glossary
(the recent discussio
The glossary in cvs docs/glossary.pod is now available on the web:
http://www.parrotcode.org/glossary
We need more tests.
According to..
http://www.hitchhiker.org/parrot_coverage/
only 33% of the lines are covered!
if something breaks in the other 67%, we'll never know, unless we have
tests.
-R
--
H.Merijn Brand writes:
>http://www.perl.org/perl6 is a bit behind. Anyone care to update and include
>apo-5? And Damian's tour info.
I've added Apoc 5.
Patches for tour info welcome.
-R
>Perhaps it got mangled? Can you send it to me as an attachment?
Attachments can also be sent to the tracker. They're handled better
now.
-R
Since we've had a few new faces around here recently, I thought it
would be a good time to remind people about www.parrotcode.org, and
specifically the Development Resources page.
http://www.parrotcode.org/resources
It looks a lot like this, but with links of course...
* Perl 6/Parrot Mail
Dan Sugalski writes:
>At 12:01 PM -0400 7/12/02, Melvin Smith wrote:
>>Did you check docs/ and docs/pdds first? There may already be something
>>there. The glossary is probably a good idea anyway.
>
>I added some definitions to glossary. I think the changes'll be
>picked up on parrotcode.org arou
>I've heard reports of rsync not working. I don't use it, so I dunno
>there. If someone's got the proper incantation, or follows the
>directions and it doesn't work (when you're *sure* you know what
>you're doing) I'll update it appropriately.
Yes, this seems broken at the moment. I've opene
>Correct, I don't maintain the site, but I believe Robert has said he would
>accept patches.
Yes, if people send me updates/diff/new content's, or just "replace
this paragraph with this", I'll do the merges.
-R
Brent Dax writes:
>[EMAIL PROTECTED]:
># Good stuff. Didn't you also send out a draft PDD about how
># types should
># be named and managed in parrot at one point? I, for one,
>
>At one point I sent out a patch to PDD7 that handled type naming.
(I don't know what happened to this specific pa
In my never-ending crusade to try and keep the bug system from passing
on lots of spam, some messages have been falsely flagged as spam.
Please look at tickets 15748 and 15877.
We've done a bunch of tweaking tonight, so hopefully the falsepos
count will drop and falseneg count will go up. In g
John Porter writes:
>
>Aldo Calpini wrote:
>> this is a little tutorial about submitting patches
>> (should be added to a FAQ, or somewhere where it's handy
>
>I think this deserves its own page somewhere on
>dev.perl.org.
Seems like a good idea. I've added it to the queue. It'll end up on
parr
>On Wed, Jul 24, 2002 at 08:44:20AM -0700, Stephen Rawls wrote:
>> The last two (well, the only two :) patches I sent
>> were counted as spam. Some of the points were becuase
Sorry about that! I'm trying to be better safe than sorry in
preventing spam from getting to the list.
>> Do the patche
>I don't like spam. Thanks for keeping it out.
I try. :)
>How do you recruit new "someone"s?
I head down to the local mall and hold up a big sign.
>Are they the same sort of "someone"s who manage perl5 bugs?
Yup.
(Or just anyone silly enough to volunteer.)
>And (IIRC) Spam Assassin is th
Bryan C. Warnock writes:
>How does one patch a file to delete?
>
>docs/a5_draft.html can go away now, thank you for playing.
rm
cvs delete
cvs commit
Bryan C. Warnock writes:
>There is a general inconsistency about file permissions throughout the
>parrot tree.
>
>Of the 80+ *.pl scripts, only 8 are 0755 - and Configure.pl isn't one of
>them. Some tests are, some aren't; and even some docs are. A list
>follows.
These have to be fixed in the re
>Ok then, [perl #16934] is unvalid, it should be removed from rt unless
>we want its syntax as an alternative to the correct way.
The removal process looks like:
set patch status to "Rejected" (and make sure to send an email
with a reason)
Change ticket state to resolved.
-R
>> xScanMail for Microsoft Exchange has blocked a file xattachment(s).
>is getting trying. Do we have any official public LARTing policy on
>braindead systems that mail back to the list?
There are too many to properly LART. When I see them, I add them to
the Spam filters. Right now we've got 1
http://www.parrotcode.org/openpatches
There are a _lot_ of Pending patches.
Within a few weeks, I hope to have an automated email nudging about
this weekly.
-R
(801) [PATCH] PerlArray in scalar context Pending
(15345) [PATCH] Generating assemble.pl Pending
(15574) [PATCH] RECALL renamed to
> Here's a couple more that I just stumbled across - they've not been
> picked up automatically because they don't have [PATCH] in the header.
> (16077) 'assign' opcode and unmorphing
> (16098) First draft of PerlScalar PMC
I've tagged them both as patches, so they'll show up in the list now.
-R
George (via RT) writes:
># New Ticket Created by George
># Please include the string: [perl #17733]
># in the subject line of all future correspondence about this issue.
># http://rt.perl.org/rt2/Ticket/Display.html?id=17733 >
Grumble. This guy sent this to the wrong email address. I've boun
>Well here it is, my first attempt at a "getting started" guide. It's
>not ready for public consumption, but I would like to hear some
When this stabilizes, we can make it available on www.parrotcode.org
>I plan to have a lot more diagrams in the document. I am using 'dia'
>to create them. I
>2.) You mention getting a Perl distribution for Windows, but don't metnion
>getting a C compiler.
> I would recommend saying something about CygWin (www.cygwin.com) or
>perhaps a dos based C compiler. cvs, perl, and make all become non-issues
>when CygWin is added to the mix; although perfo
>I'll see about getting some of the internal structures diagrammed
>better, which is the only place things are a little dodgy, but that's
>otherwise fine.
Simon Wistow <[EMAIL PROTECTED]> dropped me an email and reminded
me about AutoDia http://droogs.org/autodia/
>Now, here's hoping CVS doesn't
>>So the html is canonical and you're converting it to pod? I'm
>> confused.
>I am writing it in my own format. It lets me take notes, write todo
>lists, autogenerate the table of contents and glossary. Then I run it
>through some perl that currently spits out html and almost make pod.
Whatev
>4)How do I get pod2html to give me html that looks like the docs on
>http://www.parrotcode.org/docs/?
Ha! :)
We're using a slightly tweaked (by Graham Barr for search.cpan.org)
version of POD::POM and a stylesheet.
You can find the stylesheet here:
http://dev.perl.org/perl-styles.css
Onc
Steve Fink writes:
>> >I don't know exactly who has the permissions to do these things, but
>> >I'm pretty sure that if you have commit access then you also have RT
>> >futzing access.
^^^ this isn't true. The permissions are seperate (but obviously
should be related.)
-R
>I just wanted to obsolete this Patch, because the missing files now
>have entered the MANIFEST. But bugs6.perl.org only tells me "Permission
>denied". Im logged in, and the bugtracker recognizes this patch as
>mine.
I've tweaked the permissions, try again.
-R
Obviously spam, sorry folks.
It snuck in under the spam filters.
X-Spam-Status: No, hits=5.3 required=7.0
tests=CARRIAGE_RETURNS,FORGED_HOTMAIL_RCVD,MISSING_HEADERS,NORMAL_HTTP_TO_IP,NO_REAL_NAME,SPAM_PHRASE_00_01,TO_EMPTY
version=2.41
-R (pondering his next move in the unending war against spa
I've upgraded the experimental perl.org cvsmonitor implementation.
It's very cool. Take a peek:
http://rt.perl.org/cgi-bin/cvsmonitor/cvsmonitor.pl?cmd=viewModule&module=perl_public.parrot
-or-
http://snipurl.com/9hn
It gets updated once a day, around 3 AM Pacific time, AKA 6 AM Eastern
Time
chromatic writes:
>I've submitted three bugs for Perl 6 to [EMAIL PROTECTED] They're in
>RT, but they haven't been announced on this group. I believe Allison
>has asked Ask to look into this.
Well, since I'm the RT owner, you and she should have asked me, or
even better, the bugs6-admin at perl.
Nicholas Clark writes:
>On Thu, Nov 28, 2002 at 06:22:56PM +0100, Jerome Quelin wrote:
>> Hi,
>>
>> Would it be possible to rename the $PARROT/languages/Befunge-93
>> directory into $PARROT/languages/befunge ?
>> Indeed, as soon as parrot will support objects, I'll implement the
>> befunge 98
>Would it also be your job to do porting of subversion to VMS, so that we
>could consider replacing CVS with something that lets clients do directory
>moves? :-)
Sadly, no. :)
But I can tell you that I am actively investigating the use of
subversion for future use on perl.org projects. We're st
I've renamed the brainfuck directory to bf, per Dan's request.
I _did not_ do the usual magic I do to keep both the old and new names
valid.
Thus - according to CVS, the brainfuck directory never existed, only
one called bf.
I updated the MANIFEST, but did not update anything else.
-R
--
I've upgraded the CVS Monitor installation on perl.org
http://bugs6.perl.org/cgi-bin/cvsmonitor/cvsmonitor.pl?cmd=viewBrowse
It provides a pretty, changeset oriented view of the repositories,
with pretty graphs and stuff.
I recommend checking it out.
-R
--
>
>The checkout that rsync is returning must be getting stale.
Yeah.
Fixed.
-R
Obviously garbage. (And not related to perl6/parrot.) I've cleaned
it out of the tracker.
-R
"Vema, Venkata" (via RT) writes:
>
>g'day
> THANX IN ADVANCE
>
>**
>Btw - Is there any interest in having a GNU GLOBAL or LXR cross-referenced
>web copy of the parrot code?
Yes, definitely.
We could probably even put it on parrotcode.org or
dev.perl.org/perl6. Do you have a recommendation between GLOBAL and
LXR?
-R
>(I don't see an RT queue, so I'm sending this to the parrot queue)
There is one, but it's not visible to you. [EMAIL PROTECTED] is
the shortest address to get there.
>I have a dev.perl.org account. my email is currently set to "will at
>coleda.com".
> > For proper tracking, you should send t
Mitchell N Charity wrote:
>Do you have a recommendation between GLOBAL and LXR?
> I'd suggest LXR. It understands perl files out-of-the-box, is more
I've asked one of our volunteers who already runs some similar systems
for us if he can get this running. If not, I'll see about setting you
(
At Tue, 07 Jan 2003 18:59:22 GMT,
([EMAIL PROTECTED]) (via RT) wrote:
> # New Ticket Created by ([EMAIL PROTECTED])
> # Please include the string: [perl #19800]
> # in the subject line of all future correspondence about this issue.
> # http://rt.perl.org/rt2/Ticket/Display.html?id=19800 >
Sme
Leopold Toetsch wrote:
> $ ./getparrot
> can't create temporary directory /tmp/cvs-serv3864
> No space left on device
Oops.
Fixed.
-R
Odd.
There's not enough information in the logs to figure out what's going
on. (And the code shouldn't have this kind of failure mode.)
If it keeps happening, please keep me in the loop.
-R
At Fri, 17 Jan 2003 17:00:21 +0100,
Leopold Toetsch wrote:
> Cannot open file /tmp/#cvs.lastdir.27414
> Please reply with the best time to send your cards to her, I am lost on this one
> -Eddie
Interesting. Obviously spam. I've dealt with it.
Interesting parts, for those who care:
X-Mailer: Mach5 Mailer-3.00 PID{5df70590-1abd-4223-8406-483160352ade}
RI{38ecd-ff200} Not Licensed for UCE, uce at
> Also I can't work out how to search the list archive at develooper.com.
Patches welcome.
(Really. I have several archive management tasks that need to get
done, and if anyone wants to volunteer)
-R
> Strange. I can ssh in, and apachectl claims that the webserver is running,
> but I'm getting that error too.
>
> Ask, Robert: any ideas?
Looks like the apache had hung somewhere. I shut it down and started
it up, and it seems ok.
-R
At Thu, 06 Feb 2003 13:47:45 +0100,
Leopold Toetsch wrote:
> I don't know, why I can't update the MANIFEST, I got a fresh copy added
> CGP.pm and...
>
> $ cvs ci -mCGP MANIFEST
> cvs server: Up-to-date check failed for `MANIFEST'
> cvs [server aborted]: correct above errors first!
What does `cvs
> documentation--I'll get started on it ASAP so we can make the changes
> quickly and get this out of the way once and for all.
Famous Last Words!(tm)
-R
1 - 100 of 241 matches
Mail list logo
