Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Read-only Git, SVN Repo for Code::Blocks
oBFusCATed:
The SHA depends on the parent commit's SHA, so if the parent has different SHA the child is different, too.
I guess the histories in our repos are different, so we have different SHAs.
ollydbg:
--- Quote from: oBFusCATed on December 21, 2013, 02:53:36 pm ---The SHA depends on the parent commit's SHA, so if the parent has different SHA the child is different, too.
I guess the histories in our repos are different, so we have different SHAs.
--- End quote ---
If this is the reason, then I think I can clone your git repo(I suppose your git-svn has a full svn revisions, starting from svn rev 0), then I can use it to commit back to the SVN(https://svn.code.sf.net/p/codeblocks/code/trunk).
But I think that your git repo synchronize with the svn by hand? (not automatically?)
EDIT:
The main point is that I can have a C::B git clone(at least have the full trunk history), which I can use to directly commit back to the C::B SVN repo.
ollydbg:
FYI: Biplab's git mirror works OK, it's by my fault that use a wrong(unfixed) git, so today I run git pull command, it just fetch the whole good data again. I have updated my post here: Re: Read-only Git, SVN Repo for Code::Blocks.
ollydbg:
I found a useful webpage, which looks like to show the steps to handle the same problem(git-svn takes too long time to mirror a whole svn repo) of mine.
http://trac.parrot.org/parrot/wiki/git-svn-tutorial
--- Quote ---.......
From the leto's github mirror
Because importing all of history is *very* time consuming, DukeLeto has already gone through the trouble and maintains a github mirror of Parrot at http://github.com/leto/parrot/tree/upstream .
git clone git://github.com/leto/parrot.git
.......
Adding git-svn metadata to the github clone
.......
--- End quote ---
oBFusCATed:
--- Quote from: ollydbg on December 21, 2013, 03:03:58 pm ---But I think that your git repo synchronize with the svn by hand? (not automatically?)
--- End quote ---
Yes, but if your git svn is working you can always run "git svn rebase" to synchronize with svn and then do "git svn dcommit".
I can probably add some automatic synchronization to my repo if there is interest. I've not bothered to research how to do it, yet.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version