How can I use git as an intermediate code review stage before pushing out the remote subversion?

Question

I would like to be able to review code checked into the internal subversion repository before pushing those changes to the remote subversion server. How can I use git to stage the development subversion for review?

I have already fetched the internal subversion into git on my machine. How do I now push the changes into the remote subversion server?

Update: I am looking for a solution that allows me to pull from one subversion repository, review the code and push into a different subversion repository. Is this possible with git-svn?

Could you clarify? Are you using two separate svn servers? – Ken Liu Sep 12 '09 at 17:18 — Ken Liu, Sep 12 '09 at 17:18
@Ken: Yes. I am using two different servers. – Shoan Sep 12 '09 at 17:36 — Shoan, Sep 12 '09 at 17:36

score 3 · Accepted Answer · answered Sep 12 '09 at 20:21

3

From the git-svn manpage:

--svn-remote <remote name>

Specify the [svn-remote "<remote name>"] section to use, 
this allows multiple SVN repositories to be tracked. Default: "svn"

So add your second SVN server to your .git/config as a new [svn-remote] stanza. You can then use this option to reference it.

answered Sep 12 '09 at 20:21

ire_and_curses

68,372
23
116
141

How would I go about doing the merge and then the commit back into the svn repository? – Shoan Sep 14 '09 at 18:08

score 2 · Answer 2 · answered Sep 12 '09 at 17:30

2

Go take a look at creating patches with Git.

answered Sep 12 '09 at 17:30

cletus

616,129
168
910
942

score 0 · Answer 3 · answered Sep 12 '09 at 18:19

0

Why not just have one SVN repository with a development branch and a "blessed" branch where you merge the approved revisions to?

answered Sep 12 '09 at 18:19

Wim Coenen

66,094
13
157
251

How can I use git as an intermediate code review stage before pushing out the remote subversion?

3 Answers3