Code::Blocks

Developer forums (C::B DEVELOPMENT STRICTLY!) => Development => Topic started by: ollydbg on September 06, 2017, 04:23:23 pm

Title: C::B source code git mirror status
Post by: ollydbg on September 06, 2017, 04:23:23 pm
I try to clone C::B mirrors(I'd like to search for some commits in the whole branches).

I first try jens' git repo:
Code: [Select]
git.exe clone --progress -v "git://jenslody.de/git/codeblocks" "D:\code\cb\jen\codeblocks"

Cloning into 'D:\code\cb\jen\codeblocks'...
Looking up jenslody.de ... done.
Connecting to jenslody.de (port 9418) ... fatal: unable to connect to jenslody.de:
jenslody.de[0: 62.75.145.95]: errno=No error



git did not exit cleanly (exit code 128) (2309 ms @ 2017/9/6 22:17:37)

Then I try biplab's git repo
Code: [Select]
git.exe clone --progress -v "git://cb.biplab.in/codeblocks.git" "D:\code\cb\biplab_git\codeblocks"

Cloning into 'D:\code\cb\biplab_git\codeblocks'...
Looking up cb.biplab.in ... done.
Connecting to cb.biplab.in (port 9418) ... 130.255.190.32 done.
remote: Counting objects: 128461, done.
remote: Compressing objects: 100% (20998/20998), done.
Receiving objects:  49% (63377/128461), 32.32 MiB | 836.00 KiB/s

So, biplab's git mirror works OK.

@jens, It looks like your git repo can't be cloned?
Another issue is: it looks like the mirror on the github: jenslody/codeblocks: Git and svn mirror of the Code::Blocks svn-repo at http://svn.code.sf.net/p/codeblocks/code (https://github.com/jenslody/codeblocks) does not update for days. Is it automatically updated by some scripts?

Title: Re: C::B source code git mirror status
Post by: ollydbg on September 06, 2017, 04:55:53 pm
@biplab, it looks like the "svn" information is lost in your mirrored git, say, in each commit log message, I would like to see something like "http://svn.code.sf.net/p/codeblocks/code/trunk@11161",  the "11161" means the svn revision, I see in your mirror, there is no such information. Can you add them. Those information exists in jens' git mirror.
Title: Re: C::B source code git mirror status
Post by: oBFusCATed on September 06, 2017, 07:06:20 pm
Why do you need more than one git mirror?
If you need a reliable one, then it is up to you to make one with git svn.
Title: Re: C::B source code git mirror status
Post by: stahta01 on September 07, 2017, 03:14:45 am
@biplab, it looks like the "svn" information is lost in your mirrored git, say, in each commit log message, I would like to see something like "http://svn.code.sf.net/p/codeblocks/code/trunk@11161",  the "11161" means the svn revision, I see in your mirror, there is no such information. Can you add them. Those information exists in jens' git mirror.

If it does NOT need to be up to date you might try looking at mine;
I only update it around once a month.
Code: [Select]
https://github.com/stahta01/codeblocks_svn2git_https_metadata.gitor
Code: [Select]
https://github.com/stahta01/codeblocks_svn2git_http_metadata.git
Tim S.


Title: Re: C::B source code git mirror status
Post by: ollydbg on September 07, 2017, 03:41:45 am
Why do you need more than one git mirror?
If you need a reliable one, then it is up to you to make one with git svn.
I would like to find some commits which introduce the FineTicker Timers in our SVN history(For this discussion What is the reason that the STC(wxStyledTextCtrl) doesn't use FineTicker Timers? (https://groups.google.com/forum/#!topic/wx-users/HCEVlu-oFU4)), so I need a git repo which contains all the svn information.

currently, my own git svn repo has only limited svn revisions(it does not contains the whole history of our svn commits, I guess it is from revision > rev9000).
Title: Re: C::B source code git mirror status
Post by: oBFusCATed on September 07, 2017, 09:38:47 am
My repo has the whole history and some of the release branches.
https://github.com/obfuscated/codeblocks_sf
And they are added by Morten in some of the updates to scintilla.
Title: Re: C::B source code git mirror status
Post by: ollydbg on September 07, 2017, 10:08:07 am
My repo has the whole history and some of the release branches.
https://github.com/obfuscated/codeblocks_sf
And they are added by Morten in some of the updates to scintilla.
Interesting, I have your github repo cloned already, but I found that your repo has many svn branches missing, so later I tried to find another git repo(from jens or biplab). Do you use the git-svn to clone all the svn branches? I see biplab's repo has more branches then yours.

EDIT: I'd like to catch exact svn commit which introduce the Fine Tick timers.

Title: Re: C::B source code git mirror status
Post by: sodev on September 07, 2017, 06:17:08 pm
Well, i don't know if i missed something essential but when you are looking for a specific svn commit ... why don't you look in svn for it? Why do you need to clone the svn into git and search in the clone?!
Title: Re: C::B source code git mirror status
Post by: oBFusCATed on September 08, 2017, 12:04:03 am
EDIT: I'd like to catch exact svn commit which introduce the Fine Tick timers.
You cannot, the branch is probably long gone, because Morten tends to reuse branches, which destroys their history.
I don't know why you want to get these timers back. Let the wx guys figure this out then we'll copy them back.
Without the timers scintilla seems to work fine and Morten reported that the update to 3.6 broke badly due to bugs caused by these timers.

I don't have all the branches. Only branches that I need.
Title: Re: C::B source code git mirror status
Post by: ollydbg on September 08, 2017, 01:51:15 am
EDIT: I'd like to catch exact svn commit which introduce the Fine Tick timers.
You cannot, the branch is probably long gone, because Morten tends to reuse branches, which destroys their history.
That's bad news, so as sodev said, I have to use the pure svn to find the commit, right? In-fact, I haven't use pure svn tool for years, recent years, I use git-svn.
@sodev
The reason I like use git(git-svn) is that all the history is in my local computer, it is fast to search and navigate.

Quote
I don't know why you want to get these timers back. Let the wx guys figure this out then we'll copy them back.
OK, if I can find the svn commit, then the wx guys may be easy to apply on their wx source. :)


Quote
Without the timers scintilla seems to work fine and Morten reported that the update to 3.6 broke badly due to bugs caused by these timers.
I don't know this issue before.
Title: Re: C::B source code git mirror status
Post by: oBFusCATed on September 08, 2017, 09:22:31 am
That's bad news, so as sodev said, I have to use the pure svn to find the commit, right?
Nope. It is not present in the svn history most probably.
Have you tried looking here: https://sourceforge.net/p/codeblocks/code/HEAD/tree/branches/
There are several scintilla branches.
Title: Re: C::B source code git mirror status
Post by: ollydbg on September 08, 2017, 04:24:36 pm
I have tried stahta01's git-svn github repo(thanks stahta01) , and using the "git log -S" command to find what is the commit the code "ScintillaWX::FineTickerRunning" was added or removed to the code repo.

Code: [Select]
MINGW64 /d/code/cb/codeblocks_svn2git_http_metadata (master)
$ git log -S 'ScintillaWX::FineTickerRunning' --branches
commit 2a91a82f2acade0eacc830ab6effb6d964ecad46
Author: mortenmacfly <mortenmacfly@2a5c6006-c6dd-42ca-98ab-0921f2732cef>
Date:   Sat Aug 30 19:34:27 2014 +0000

    * prepare branch for merge to trunk

    git-svn-id: http://svn.code.sf.net/p/codeblocks/code/branches/scintilla_3_5_0@9893 2a5c6006-c6dd-42ca-98ab-0921f2732cef

commit 52b93bb6054a0688ac5d2c0b5ffaf71c7530fec5
Author: mortenmacfly <mortenmacfly@2a5c6006-c6dd-42ca-98ab-0921f2732cef>
Date:   Tue Aug 26 07:25:56 2014 +0000

    * added / updated (wx)Scintilla lib to v3.5.0 for testing purposes -> use special project file CodeBlock.scintilla.cbp and RE-compile!

    git-svn-id: http://svn.code.sf.net/p/codeblocks/code/branches/scintilla_3_5_0@9861 2a5c6006-c6dd-42ca-98ab-0921f2732cef

So, there are two commits. I have even install the tortoisesvn to see the pure svn repo change logs, but I don't see much methods that I can search on the SVN repo like the "git log -S" command.

I believe the commits r9861 and r9861 are the correct svn commit to introduce the timers. :)


Title: Re: C::B source code git mirror status
Post by: oBFusCATed on September 08, 2017, 09:08:31 pm
Probably yes, but they are not minimal commits that introduce timers only...