J.C.Wren wrote:
> The step to copy the gcc/gcc-3.3 files to the gcc-3.2.3 is not clear
> for new
> users. I would suggest adding an example....
>
Y'know, the step of copying gcc-3.3 files to a gcc-3.2.2 directory isn't
exactly clear to *experienced* users either! I mean, OK, so an experienced
person probably read the README first, but it wan't exactly an obvious step,
and it does leave you with the thought of "omygawd, I'm patching 3.2.3 with
3.3 files, will it really work?".
Could we not have a CVS directory called gcc/gcc-3.2.3 even if it is merely
symlinked to gcc/gcc-3.3 currently? That makes the copy operation look more
"natural" and less like a mad kludge.
Later, when there are real gcc-3.3 specific patches, the gcc-3.3 and gcc-3.2.3
subdirectories can be changed from being symlinks to each other and the
new stuff goes in the specific gcc-3.3 directory.
Seems much more obvious to me....
--
Steve Hosgood |
st...@caederus.com | "A good plan today is better
Phone: +44 1792 203707 + ask for Steve | than a perfect plan tomorrow"
Fax: +44 70922 70944 | - Conrad Brean
--------------------------------------------+
http://tallyho.bc.nu/~steve | ( from the film "Wag the Dog" )
