For 1 and 2: This is a great idea.  What about having a tool in CVS that
would use the RegEx classes to ensure that the file structure matches
(roughly) the structure we're expecting, ie: replace all tabs w/spaces,
replace all text before the first "using" keyword with the
#region-wrapped license, etc.

Just a comment about the $Log$ keyword - the CVS in-line version log is
a little bit of a pain to handle sometimes.  I think it would be okay if
wrapped in a #region, but some issues may crop up (especially with
regards to merging/branching).  This page mentions some of the issues
with the $Log$ keyword:

http://developer.apple.com/darwin/tools/cvs/cederquist/cvs_96.html

On Wed, 2003-03-12 at 02:24, Scott Hernandez wrote:
> I want to reformat all the files and do the following:
>  
> 1.) Wrap the license info at the top of the file in a #region, which
> will make editing with vs.net (and others I believe). 
>  
> 2.) Reformat all files removing tabs and following the guidelines in
> the nant coding
> conventions.(http://sourceforge.net/docman/display_doc.php?docid=6080&group_id=31650).
>  
> 3.) Insert cvs substitution keywords that will help build a history
> log in each file. (http://www.cvshome.org/docs/manual/cvs_12.html) (I
> will look into making this part of the xml docs for revision history.)
>  
> So, before we go through this work, any one have any more ideas? If
> this doesn't happen now, I would like to see it happen before a .9
> release.
>  
> Is there anything else we should do (other than coding, code reviews,
> testing, and releases :) along these lines? 
-- 
Matthew Mastracci <[EMAIL PROTECTED]>


-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open! 
Get cracking and register here for some mind boggling fun and 
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
_______________________________________________
Nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

Reply via email to