httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "William A. Rowe, Jr." <wr...@lnd.com>
Subject RE: cvs commit: apache-1.3/src/helpers dsp5tocvs.pl cvstodsp5.pl
Date Thu, 08 Jun 2000 02:50:20 GMT
> From: wrowe@locus.apache.org [mailto:wrowe@locus.apache.org]
> Sent: Saturday, June 03, 2000 1:37 AM
> 
> wrowe       00/06/02 23:36:45
> 
>   Added:       src/helpers dsp5tocvs.pl cvstodsp5.pl
>   Log:
>     I imagine everyone who cares recognizes what this implies.  Absent any
>     objections, the patch to bring the 1.3.x tree up to Visual C 6.0 .dsp
>     format will be committed on Tuesday night, prior to the 1.3.13 release.
>   
>     I strongly suggest, however, that we maintain the 5.0 version .mak,
>     since VC 6 will easily recognize it, and the additional features
>     offered by the /ZI flag are rather mute for folks who don't work in
>     the VisualStudio development environment.  And so, 5.0 .mak files will
>     be regenerated and diffs submitted that evening, as a just-in-case.

Ok, exactly one comment so far (Greg's), and I posted a list of advantages
and disadvantages.

Nobody feels one way or another, then?

If so (since I'm working in both trees) I'd like them in sync in terms of
working with the tree.  If you object, vote -1.  Then I will rename these
macros appropriately (dsp6tocvs.pl and cvstodsp6.pl, respectively).

If I have no objections tommorow a.m. I will commit translated .dsp's. 

Revised docs on the translation will be committed in either case by Friday. 

Bottom line, if you aren't working the tree, both 5.0 and 6.0 are 
interchangable, except that 5.0 users would have to change the debug option
themselves (or run the .pl to do it for them) since /ZI is unknown to 5.0,
and 6.0 receives a warning that the projects are being converted to 6.0.

All in all, not big things.  Just a pain in keeping the cvs tree in sync
with one project one way, and the other project backwards.


Mime
View raw message