RE: [cdt-dev] Re: [cdt-patch] Scanner Updates 3/10/03

["Schaefer, Doug" <dschaefer@xxxxxxxxxxxx>]

My experience with other projects is that ChangeLogs don't show changes to
every file in a project, but only the highlights from release to release.
The level we are talking about here could just as easily be gathered by
walking through the CVS history (even with an automated report generator).
Duplicating this in the ChangeLog is a waste of time and I don't think it
gives the information that people are looking for with ChangeLogs.  I'd
rather only see significant design changes noted there only.


Doug Schaefer
Senior Staff Software Engineer
Rational Software - IBM Software Group
Ottawa (Kanata), Ontario, Canada
 

-----Original Message-----
From: Alain Magloire [mailto:alain@xxxxxxx] 
Sent: Tuesday, March 11, 2003 11:35 AM
To: cdt-patch@xxxxxxxxxxx
Cc: cdt-dev@xxxxxxxxxxx
Subject: [cdt-dev] Re: [cdt-patch] Scanner Updates 3/10/03

> 
> This message is in MIME format. Since your mail reader does not understand
> this format, some or all of this message may not be legible.
> 
> ------_=_NextPart_000_01C2E73C.BC1768E0
> Content-Type: text/plain;
> 	charset="iso-8859-1"
> 
> - added in support for detecting and reporting circular inclusions
> - added optimization by caching inclusion directories
> - added macro pasting capabilities and tests
> - updated inclusion searching algorithm for local inclusions
> 

A general comment.

The change logs should be in a ChangeLog file, for easy tracking.
You could create the ChangeLog file in the source folder, for example, in
the parser
directory if that make things easier and reduces collisions.

The ChangeLog policy was from a board member, the suggestion was passed
along and
put in to vote.  If we are not going to go through this, may as well voted
down.



_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cdt-dev