Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Read-only Git, SVN Repo for Code::Blocks
ollydbg:
--- Quote from: Biplab on April 16, 2013, 05:30:49 pm ---Do you have appropriate access to repo? AFAIK, you need special access to change commit log.
--- End quote ---
I don't have special access, just normal developer R/W access to SF repo.
Jenna:
If I understand it correcty, the change of the log-entry is in fact a property change.
ANd such changes have normally to be committed explicitely.
ollydbg:
--- Quote from: jens on April 17, 2013, 06:26:53 am ---If I understand it correcty, the change of the log-entry is in fact a property change.
ANd such changes have normally to be committed explicitely.
--- End quote ---
Thanks, but currently I don't find any option in TortoiseSVN that let me commit such property change. :)
MortenMacFly:
--- Quote from: Biplab on April 16, 2013, 05:30:49 pm ---Do you have appropriate access to repo? AFAIK, you need special access to change commit log.
--- End quote ---
Nope, not at all. I've setup a general hook that does not depend on user rights (although it would be possible to do that, too).
Also, a log change does not require an explicit commit - its done directly.
BUT: Your SVN software needs to re-cache the log messages. As these are usually stored locally to save bandwidth, you need to ensure they get re-freshed. For me this is done automatically, for TortoiseSVN this may not be the case. The easiest (but brute-force) way would be do delete the SVN log cache for the particular repo. Then it will be re-built completely.
oBFusCATed:
--- Quote from: MortenMacFly on April 17, 2013, 07:36:52 am ---Also, a log change does not require an explicit commit - its done directly.
--- End quote ---
And it my opinion this is the reason this feature should be disabled. A person can destroy the history and we won't know about it. Good luck in restoring it back.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version