1) I'll start merging branches/leo-ctx5 back to trunk soon.
- The merge isn't a merge, but a switch
- Please refrain from svn checkins until this is finished
- I'll send another note, when it's done
2) Thereafter the trunk remains feature-frozen
- no new feature checkins please
- bugfixes and
Leopold Toetsch wrote:
3) Release will follow at the weekend
It's none of my business I know, but why not give the release a more
realistic number (e.g. 0.7.0)?
People tend to extrapolate that if it took 5 years to get to 0.2.3 then
it will take another 16 years to get to version 1.0.
Regards,
On Tue, Sep 27, 2005 at 01:49:52PM -0700, Chip Salzenberg wrote:
On Mon, Sep 26, 2005 at 03:29:52PM -1000, Joshua Hoblitt wrote:
An updated patch is attached.
All OK now with me, thanks.
The ASCII art of the 'padding' was wrong. A corrected patch is
attached.
-J
--
Index:
Roger Browne wrote:
Leopold Toetsch wrote:
3) Release will follow at the weekend
It's none of my business I know, but why not give the release a more
realistic number (e.g. 0.7.0)?
People tend to extrapolate that if it took 5 years to get to 0.2.3 then
it will take another 16 years to get
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
On Sep 28, 2005, at 10:50, Leopold Toetsch wrote:
1) I'll start merging branches/leo-ctx5 back to trunk soon.
- The merge isn't a merge, but a switch
- Please refrain from svn checkins until this is finished
Step 1) finished. All the merits and thanks belong to Robrt and clkao.
Robert did
Leo's proposed syntax is fine with me.
[leo - Fri Feb 25 01:34:24 2005]:
Bernhard Schmalhofer [EMAIL PROTECTED] wrote:
Hi,
in the near, or far, future there will be test scripts and compiler
input in PIR. For that it would be nice, if long text doesn't have to
be crammed into a
Guys,
I've been wanting to relax the dependency that parrot's core has on
parrot_config. As things stand at the moment, src/global_setup.c makes
a call to parrot_get_config which is linked into the executable itself
by selecting either null_config.o, parrot_config.o or
install_config.o.
This
