> Joakim Tjernlund <Joakim.Tjernlund@transmode.se> wrote:
quoted text > > Eric Wong wrote:
> > > I would do something like this:
> > >
> > > ... (same stuff as above before with svn setup...)
> > > git clone $ORG_REPO $GIT_REPO
> > > cd $GIT_REPO
> > > git-svn init "$REPO"/trunk
> > > git-svn fetch
> > >
> > > # sync the SVN repo with initial-uboot
> > > # this will just commit a snapshot, without history,
> which I assume
> > > # is what you want.
> > > git-branch initial-uboot f5e0d03970409feb3c77ab0107d5dece6b7d45c9
> > > git-svn commit initial-uboot
> > > git checkout -b svn-branch remotes/git-svn
> > > git-pull . tmcu2
> > >
> > > # this should work assuming the path from
> initial-uboot..tmcu2 is linear
> > > # use gitk initial-uboot..tmcu2 to check
> > > git-svn dcommit
> >
> > Great! This was exactly what I wanted, thanks. I never
> realized that one should
> > do git-svn commit initial-uboot to get that single commit.
> > I also replaced git-svn dcommit with git-svn commit
> remotes/git-svn..svn-branch
> > as I don't have that version yet.
> >
> > You should add this as an example I think.
> >
> > Can I ask for an example that used multi-init and
> multi-fetch? I tried, but
> > could not make it work.
>
> git-svn multi-init
https://svn.musicpd.org/mpd -T trunk -t tags -b branches
> git-svn multi-fetch
This is how far I got too(sorry for beeing unclear). It is the
remaing bits that I got stuck on. How would the remaining git-svn
commands look like in the above example?
quoted text >
> In the latest git-svn (should be in 1.4.3), you can re-run 'git-svn
> multi-init' with no arguments to discover new tags+branches.
>
> Anybody willing to supply patches for better documentation? I'll be
> quite busy with other projects the next two weeks, asciidoc is quite
> slow for me; but I'd like to have better docs for git-svn in 1.4.3.
That would be great, I am still very much in the dark.
Jocke
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to
majordomo@vger.kernel.org
More majordomo info at
http://vger.kernel.org/majordomo-info.html