Eric Wong <normalperson <at> yhbt.net> writes:
...
>
> Hi Fabian,
>
> Since you don't want to track the entire repo and these seem like
> unrelated (history-wise) trees, you probably want the simplest cases:
>
> git svn clone svn://example.com/path/to/xapplication2
> git svn clone svn://example.com/path/to/aa/bb/cc/xapplication1
>
> These commands are like doing the following with plain old svn:
>
> svn co svn://example.com/path/to/xapplication2
> svn co svn://example.com/path/to/aa/bb/cc/xapplication1
>
> > I tried to use "git config svn-remote.svn.branches" to do this,
> > please see in function "do_git_svn" in bash-script - but no success
>
> svn-remote.svn.branches and tags are really only for repos with
> standard layouts.
>
Hello Eric,
hmm, understand,
but this just does an checkout to the working dir
the reason for using git is:
- work offline, with (at least read) access to all the svn branches
- have some more (privat, not commit back to svn) branches for experiments
- all the nice git stuff ..
regards,
Fabian
--
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