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

Re: Hot backup changes

From: Branko Čibej <brane_at_xbc.nu>
Date: 2002-08-22 18:32:35 CEST

cmpilato@collab.net wrote:

>=?UTF-8?B?QnJhbmtvIMSMaWJlag==?= <brane@xbc.nu> writes:
>
>
>
>>>I do need to sweat the log stuff doing the incremental backups.
>>>
>>>I plan on replacing the db backup solution with the svnadmin dump based
>>>backup solution due to the large disk space that the db based backups
>>>are using, I indicated my the first message in this thread.
>>>
>>>So this needs to be a real backup solution. Having a dump solution that
>>>has old log messages in it is not an acceptable solution.
>>>
>>>
>>>
>>Why not just add an option to tweak-log.cgi to have it re-dump a
>>revision when it changes its log message? I think that's the simplest
>>possible solution, has no extra overhead, and does exactly what you want.
>>
>>
>
>Well, that would only be triggered if tweak-log.cgi was the mechanism
>by which the log changed. That isn't always going to be the case. In
>fact, you can't even be sure that svnadmin is the tool doing the
>modification.
>
Hm, and changing the log message does not represent a commit, obviously.
Which means even a hook script wouldn't help. How boring.

Do we need a post-change-unversioned-item hook?

-- 
Brane Čibej   <brane_at_xbc.nu>   http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Aug 22 18:33:22 2002

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.