[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Commit Log File

From: <kfogel_at_collab.net>
Date: 2003-05-13 17:25:40 CEST

mark benedetto king <mbk@boredom.org> writes:
> This is covered in:
> http://subversion.tigris.org/issues/show_bug.cgi?id=958

I have since realized that this would be *very* hard to implement.

For repository specialists, here is the explanation:

The problem is that the file in the txn needs to know its contents
before the txn can be finalized. For normal keywords, this is no
problem -- the keywords are stored contracted anyway. But for the
proposed one-time-only revision keyword, we'd need to know the
revision number of the commit *before* the commit is done. That
effectively means locking up the revision number, then going back and
modifying all the files in the txn that have this special keyword,
then finishing the commit. Yuck.

So I doubt issue #958 is going to be resolved anytime soon (I'll add
these comments to the issue).

Jonathan, I'd recommend that you not store your logfile statically
anymore. Instead, have a script that can generate the file
automatically, for example by running 'svn log -v' and massaging the


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue May 13 18:09:03 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.