You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Karl Fogel <kf...@newton.ch.collab.net> on 2002/08/23 01:52:44 UTC
Re: svn commit: rev 3033 - trunk trunk/subversion/include
Greg Stein <gs...@lyra.org> writes:
> > * CHANGES: Bump minimum revision.
>
> I don't understand the churn on this file. Why keep bumping this? Why not
> just leave it as ??? until we have a revision?
Every time I do a release, I try to get the CHANGES revision close.
And every time, you complain about it :-).
The answer:
We might as well have some information there as early as possible, so
someone reading the CHANGES file _right now_ will know whether or not
their commit made it in or not.
I'm sitting here waiting for dav tests to pass, or whatever. There's
a small window during which I can't do anything else useful, and all
my mail is read. So.... Might as well take care of this; it won't
hurt anything, and it might help someone. (And in the particular
commit you quote above, we had to make a new revision anyway to get
the SVN_VER_MICRO change, so there's no reason not to up CHANGES as
well.)
-K
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org