[perl #34548] [TODO] Replace classes/pmc2c.pl with classes/pmc2c2.pl
Bernhard Schmalhofer via RT
>
> pmc2c2.pl is the new pmc2c.pl. Both currently exist in Parrot CVS.
> Either pmc2c.pl should be deleted or pmc2c2.pl should be renamed to
> pmc2c.pl.
A better location might be 'build_tools/pmc2c.pl*, as the script is also
used in 'dynclasses/build.pl'. It propably will also be used for for
their language specific PMCs in 'languages/<lang>'.
Should we wait for that, until it is decided whether we will switch to
SVN? I think that SVN preserves change history for moved files.
--
/* Bernhard.S...@gmx.de */
Matt Diephouse
# Please include the string: [perl #34548]
# in the subject line of all future correspondence about this issue.
# <URL: https://rt.perl.org/rt3/Ticket/Display.html?id=34548 >
pmc2c2.pl is the new pmc2c.pl. Both currently exist in Parrot CVS.
Either pmc2c.pl should be deleted or pmc2c2.pl should be renamed to
pmc2c.pl.
--
matt diephouse
http://matt.diephouse.com
Leopold Toetsch
>> [mdiep - Di 22. Mär 2005, 14:35:02]:
>>
>> pmc2c2.pl is the new pmc2c.pl. Both currently exist in Parrot CVS.
>> Either pmc2c.pl should be deleted or pmc2c2.pl should be renamed to
>> pmc2c.pl.
> A better location might be 'build_tools/pmc2c.pl
Yep.
> Should we wait for that, until it is decided whether we will switch to
> SVN? I think that SVN preserves change history for moved files.
That's the question. Are we switching to SVN?
leo
Matt Fowles
I vote yes.
Matt
--
"Computer Science is merely the post-Turing Decline of Formal Systems Theory."
-???
Matt Diephouse
> Matt: Could you check whether all changes are in?
Looks good to me. Thanks.
Bernhard Schmalhofer via RT
> > >> pmc2c.pl.
> >
> > > A better location might be 'build_tools/pmc2c.pl
> >
> documentation changes. Note that these changes involved using 'svn rm'
> and 'svn mv'. Hopefully the patch DWIW and moves/removes the files.
Applied the patch. with some fiddling.
Matt: Could you check whether all changes are in?
--
/* Bernhard.S...@gmx.de */