Re: [PATCH] branches/wc-replacements: write relative path in working copy log

> Er, I think you must have misread what I said. Comments in the code should
> certainly indicate why the code does what it did ... but not why it was changed
> from some previous behaviour. Comments about changes to the code belong in the
> change management system, don't they?
>
> So, in this case, the code could say "We use a relative path here as specified
> in the design document" (though that's presumably implicit and redundant), and
> the change log should say something to the effect of, "Changed to a relative
> path because it was previously contravening the documented design."

Done.

bye,

Erik.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Sep 5 23:15:55 2005