Noel,

> As for the rest of it, I'm sure that Paul isn't doing anything
intentional
> to cause more work for anyone.  If he is seeing anomalous behavior, it
is
> probably worth investigating why something is causing a problem.

The issue isn't whether Paul is doing anything intentional.  Certainly
that's not the case.  And I certainly don't have an issue with him
investigating why he's getting this anomalous behavior.  The issue is
whether there is a problem with the James build.  Paul concluded that
there is.  I'm sure he's wrong, and I've given my reasons.  Until and
unless some one can counter those reasons, I'm going to assume that it's
an issue with Paul's environment.

I asked for Paul to be more restrained in his commits, filtering them by
eye rather than trusting his CVS client.  That way he doesn't make more
work for the other committers and clutter up the CVS logs.  Honestly, I
don't think that's unreasonable.
 
> I know that I used to see that CRLF problem with build.bat all the
time
> because it didn't have the CRLF in the CVS.  RECENTLY I've seen a
> "problem"
> where some of the files I've worked on have changed during a build.
This
> turns out to be fine: the "change" was the removal during build of
tabs I
> had introduced and hadn't yet removed prior to making a patch, so it
isn't
> a
> problem at all.

You know the tab issue isn't related.  The CVS source files are not
supposed to contain tabs, and hence a recent modification to the build
was designed to ensure that they were eliminated from the source files.
This was intended to eliminate the need for the committers to crawl
through the files removing tabs.  It was a recent addition and required
a few commits to get spurious tabs out of CVS.  Once that was done,
running a build didn't introduce any new diffs. 

No one is contending that the build doesn't change source files.  It
does, but does so in a well defined way that is clear from the Ant
tasks.  And I also contend that those Ant tasks are correct.

--Peter 



--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to