Re: Adding Revision Number to Changes file comment

On Wed, Feb 07, 2007 at 05:50:44PM -0600, Ryan Schmidt wrote:
> On Feb 7, 2007, at 15:53, Jeff Smith wrote:
>
> >On Wednesday 07 February 2007 14:46, Jeff Smith wrote:
> Do NOT modify any file in a pre-commit hook. The server has no way of
> informing the client that such a modification has taken place, and
> then the server's idea of what the revision looks like is different
> from the client's, which will lead to badness. So do not do this.

I thought that would be a problem. It would be a handy feature,
although svn blame can be used just as well to find out which revision
goes with each entry in the Changes file.

> Bill, I don't think there's any way to do what you want in
> Subversion. May I recommend that you record your changes in the svn
> commit log as usual, then later, when you want to cut a release, you
> can create a changelog from the Subversion log, for example using a
> tool like svn2cl?

That's probably what makes the most sense. The comment in the svn
check-in isn't always the same comment that goes in the Changes file,
though. Should be, but doesn't always work out that way.[1] ;)

I suppose I could do a svn update to see the current revision number
and use that plus one (hoping that nobody else makes a commit in
between).

Another approach is just make sure there's a (trac) ticket for the
changes and reference that in the Changes file. "Closes #1332"

[1]
Changes: Added patch to add feature kindly provided by user Y.

Log: Added patch that Y posted to the list five time. Hopefully
that will keep Y quiet for a few days.

Log: Added missing file that forgot to svn add from last commit.

Log: Rewrite patch so it actually works as documented.

</wink>

-- 
Bill Moseley
moseley@hank.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org