I was prepared to put up with it not being a bare repository (asides
the extra /.git/ in the URL it's pretty much the same).
On the git host I'd set refs/heads/trunk to be
ref: refs/remotes/svn/trunk
And I'm hoping that a cron of git svn fetch ; git-update-server-info
will do the trick. It appeared to keep it in sync when I fetch
downstream. I don't know if I'm being naive though expecting that to
work as I don't grok all that git-svn needs to work properly - but I'm
working on it ;-)
My current plan is for developers to push/pull to git to share amongst
the git-devs, and to push to svn when wanting to share with everyone
else..
[svn user] ---(ci/co)--->[svn] --pull--> [git]
^ ^
| |
push push/pull
| |
---[git user]----
On Dec 19, 2007 8:23 PM, Miklos Vajna < vmiklos@xxxxxxxxxxxxxx> wrote:
> On Wed, Dec 19, 2007 at 12:54:47PM -0500, Steven Walter < stevenrwalter@xxxxxxxxx> wrote:
> > Using a central git repo that is kept uptodate with svn is the approach
> > I've used. git-svn isn't especially keen on this mode of operation,
> > however. After every fetch, you have to reset refs/remotes/trunk to
> > origin/master, which it turn puts .git/svn out of date (you can blow it
> > away and run "git svn fetch" to regenerate it).
>
> an other problem is that you probably want to have a bare repo while
> git-svn needs a working dir. a possible solution:
>
> http://blogs.frugalware.org/vmiklos/2007/12/09/p320
>
> (it works for me fine, but maybe there are problems with it so use with
> care :) )
>
> - VMiklos
>
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
