Read-only Git, SVN Repo for Code::Blocks

[Biplab]

Also, a log change does not require an explicit commit - its done directly.

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.

I second oBFusCATed. This feature should not be enabled on our repo.

[MortenMacFly]

A person can destroy the history and we won't know about it.

Nope - how would you want to do that?

Well we should trust each other at least that much that we don't select >8000 commits and change their commit log. Its only possible for one entry at a time and is an atomic operation. So it cannot interfere with any other operation.

So: Do you think we need to disabled it because one of us well be that bad to change all our logs one-by-one? If so, we can close commits all-together, cause you could also just commit bad stuff.

[oBFusCATed]

If so, we can close commits all-together, cause you could also just commit bad stuff.

Yes, but we can revert them, because we have the old state or the repo. With this option there is not way to revert the change.

[MortenMacFly]

With this option there is not way to revert the change.

Well you still have a backup.

But again: Why would you want to do that? Its enabled that you can change your own commit messages if you made a mistake and maybe before a release to auto-process changelogs more easily. Thats convenient enough I'd say. And I already changed some of my mistakes in the SVN log which made me happy. You want to see me happy, don't you?! :-)

[ollydbg]

With this option there is not way to revert the change.

Well you still have a backup.

Where is the backup? A GIT mirror?

But again: Why would you want to do that? Its enabled that you can change your own commit messages if you made a mistake and maybe before a release to auto-process changelogs more easily. Thats convenient enough I'd say. And I already changed some of my mistakes in the SVN log which made me happy. You want to see me happy, don't you?! :-)

Good to see that One can only change his own committed message.

BTW: I tried many times, many options (include disable cashing) under TortoiseSVN, but all failed, so I'm going to try SVN command line.

[MortenMacFly]

Where is the backup? A GIT mirror?

A SVN dump made all night directly as SF.

[ollydbg]

SVN command line show that the log message are already changed:

E:\code\cb\cb_trunk_sf>which svn
D:\Program Files\TortoiseSVN\bin\svn.EXE

E:\code\cb\cb_trunk_sf>svn log -r 8855
------------------------------------------------------------------------
r8855 | ollydbg | 2013-02-25 13:00:49 +0800 (星期一, 25 二月 2013) | 1 line

* exchndl: link libz instread of libintl, thus implement the Feature Request #55
17. Add checking winnt.h macros for both MinGW and MinGW-W64. Workaround a #erro
r in bfd.h.
------------------------------------------------------------------------

E:\code\cb\cb_trunk_sf>

But I still see http://sourceforge.net/p/codeblocks/code/8855/ shows:

exchndl: link libz instread of libiberty, thus implement the Feature Request #5517. Check winnt.h for both MinGW and MinGW-W64. Workaround a #error in bfd.h.

So, any one can help me?

[Jenna]

It looks like sourceforge caches (at least) the history-entries and do not update them if they get changed.

[ollydbg]

I post a Ticket in SF, see: https://sourceforge.net/p/forge/site-support/3691/
Hope they can fix it.

EDIT: It looks like SF guys will look into it soon, see the IRC messages.

   ollydbg   Anyone encountered a problem that I change the SVN log message for one revision, but the SF repo does not update this message, thanks.
   wjp   can you be more specific?
   ollydbg   Hi, wjp, thanks.
   ollydbg   I'm a developer of Codeblocks.
   ollydbg   Then, I found that one commit of mine has some typos, so I try to change the log message under TortoiseSVN. Just click on one revision's log message, then select the change log message menu.
   ollydbg   So, I can successfully change the log message. Yes, we have already enabled the svn-hook in SF site, so this let our Codeblocks change log message.
   ollydbg   But when I look at the SF svn web page, it still show the old log message, so I suspect it was some bug on SF. (AS we have discussed this issue for two days, other Codeblocks also suspect it was a bug of SF), does any one encountered the same issue like me? Thanks.
   -->|   mlohr (~mlohr@ultrabook.at.home.ml.vg) has joined #sourceforge
   ollydbg   You can read my post in this post from Codeblocks forum: http://forums.codeblocks.org/index.php/topic,16096.msg121965.html#msg121965, here you see different message from my local svn log command and the SF svn web page.
   ollydbg   I have also create a Ticket in SF minutes ago, see: https://sourceforge.net/p/forge/site-support/3691/
   ollydbg   Thanks.
   wjp   if you had the pre-revprop hook already, that does sound like a probable SF issue. It's still outside of ,,businesshours , but someone from SF should be in soon
   gribble   Sourceforge.net business hours are approximately 12:00 to 21:00 UTC, excluding weekends and holidays. Currently, it is Fri Apr 19 08:45:17 2013 UTC.

[MortenMacFly]

It looks like sourceforge caches (at least) the history-entries and do not update them if they get changed.

I am not so sure about that - for me it worked instantaneously. I would believe its more a bug with TortoiseSVN... or feature.

[Jenna]

It looks like sourceforge caches (at least) the history-entries and do not update them if they get changed.

I am not so sure about that - for me it worked instantaneously. I would believe its more a bug with TortoiseSVN... or feature.

No, surely not, becuase in svn it's changed (as svn-log shows), but sf's websvn does not sgow the changes.
In other word the webserver shows another comment than the real svn-client.
That is surely a bug in sf's software.

[stahta01]

From http://sourceforge.net/p/codeblocks/code/8855/

exchndl: link libz instread of libintl, thus implement the Feature Request #5517. Add checking winnt.h macros for both MinGW and MinGW-W64. Workaround a #error in bfd.h.

Are you sure its NOT a local PC browser save issue?
Or maybe it just takes a while to be fixed to make to Web Server? (Web server updates the log on a hourly or daily basis type issue.)
Or did the fix it just a few minutes ago?

Tim S.

[Jenna]

It's there now, but was not yesterday, with empty browser cache.

Such webservices can use local caches, but such a cache might not always work correctly

Looking at the ticket opened by ollydbg, it seems it was fixed by sf-maintainers.

[Alpha]

Biplab, is it possible to make the age column in your mirror look more like it does on berliOS?

[Biplab]

Biplab, is it possible to make the age column in your mirror look more like it does on berliOS?

Done.