I currently have a bare repo to be used by a development team for
maintaining a project with git. I have a fetch repo which was
created using git-svn.
The fetch repo gets the updated information from the central svn
repository using
git svn --all
git push origin --mirror
This lets me pick up
There is a typo below:
On Mar 22, 1:14 pm, Sabba Hillel sabbahil...@gmail.com wrote:
I currently have a bare repo to be used by a development team for
maintaining a project with git. I have a fetch repo which was
created using git-svn.
The fetch repo gets the updated information from the
Just to be clear, the upci alias is explained
here: http://blog.tfnico.com/2010/11/git-svn-mirror-for-multiple-branches.html
It's defined as:
upci = !git update-ref refs/remotes/$(git branch | grep '^*' | awk '{print
$2}') refs/remotes/origin/$(git branch|grep '^*'|awk '{print $2}') git
svn
Thanks. Unfortunately I do have a lot of branches. Actually, the fetch
does pick up all branches and sends them to the bare repository so
that every fetch updates every branch. So far it is only the dcommit
that is giving the problem. I am trying to avoid having to get
everyone use a git svn
On Tue, Mar 22, 2011 at 1:36 PM, Thomas Ferris Nicolaisen
tfn...@gmail.com wrote:
Thanks. Unfortunately I do have a lot of branches. Actually, the fetch
does pick up all branches and sends them to the bare repository so
that every fetch updates every branch. So far it is only the dcommit
that
The trick is to first clone the bare repository, and then do a git svn init
inside it, so it can be used for dcommitting.
There are two ways to set up a repository that you can dcommit from:
1) git svn clone (takes ages with big repositories)
2) git clone existing repository, and then do git
On Tue, Mar 22, 2011 at 6:38 PM, Thomas Ferris Nicolaisen
tfn...@gmail.comwrote:
The trick is to first clone the bare repository, and then do a git svn init
inside it, so it can be used for dcommitting.
There are two ways to set up a repository that you can dcommit from:
1) git svn clone
