* how does git svn work
@ 2008-06-30 19:57 Thomas Koch
0 siblings, 0 replies; 3+ messages in thread
From: Thomas Koch @ 2008-06-30 19:57 UTC (permalink / raw)
To: Git Mailing List
Hi,
is there a document explaining the internals of GIT-SVN? I'd like to
know, which SVN commands are executed in the background and how git-svn
recognizes branch creation in SVN.
In particular I want to follow the repository at:
http://pubsvn.ez.no/nextgen/
The layout is like
/trunk
/stable
|- 4.0
|- 3.9
|- 3.8
...
/releases
|- 4.0
|- 4.0r1
|- 3.9
|- 3.9r1
|- 3.9r2
I do not know, whether git-svn can create branches automatically for
each directory under /stable and one main branch for trunk or whether I
need to create one svn-remote definition for every svn directory I want
to track.
Best regards,
--
Thomas Koch, Software Developer
http://www.koch.ro
Young Media Concepts GmbH
Sonnenstr. 4
CH-8280 Kreuzlingen
Switzerland
Tel +41 (0)71 / 508 24 86
Fax +41 (0)71 / 560 53 89
Mobile +49 (0)170 / 753 89 16
Web www.ymc.ch
^ permalink raw reply [flat|nested] 3+ messages in thread
* how does git svn work
@ 2008-06-30 19:57 Thomas Koch
2008-06-30 20:57 ` Brian Gernhardt
0 siblings, 1 reply; 3+ messages in thread
From: Thomas Koch @ 2008-06-30 19:57 UTC (permalink / raw)
To: Git Mailing List
Hi,
is there a document explaining the internals of GIT-SVN? I'd like to
know, which SVN commands are executed in the background and how git-svn
recognizes branch creation in SVN.
In particular I want to follow the repository at:
http://pubsvn.ez.no/nextgen/
The layout is like
/trunk
/stable
|- 4.0
|- 3.9
|- 3.8
...
/releases
|- 4.0
|- 4.0r1
|- 3.9
|- 3.9r1
|- 3.9r2
I do not know, whether git-svn can create branches automatically for
each directory under /stable and one main branch for trunk or whether I
need to create one svn-remote definition for every svn directory I want
to track.
Best regards,
--
Thomas Koch, Software Developer
http://www.koch.ro
Young Media Concepts GmbH
Sonnenstr. 4
CH-8280 Kreuzlingen
Switzerland
Tel +41 (0)71 / 508 24 86
Fax +41 (0)71 / 560 53 89
Mobile +49 (0)170 / 753 89 16
Web www.ymc.ch
--
Thomas Koch, Software Developer
http://www.koch.ro
Young Media Concepts GmbH
Sonnenstr. 4
CH-8280 Kreuzlingen
Switzerland
Tel +41 (0)71 / 508 24 86
Fax +41 (0)71 / 560 53 89
Mobile +49 (0)170 / 753 89 16
Web www.ymc.ch
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: how does git svn work
2008-06-30 19:57 how does git svn work Thomas Koch
@ 2008-06-30 20:57 ` Brian Gernhardt
0 siblings, 0 replies; 3+ messages in thread
From: Brian Gernhardt @ 2008-06-30 20:57 UTC (permalink / raw)
To: Thomas Koch; +Cc: Git Mailing List
On Jun 30, 2008, at 3:57 PM, Thomas Koch wrote:
> In particular I want to follow the repository at:
> http://pubsvn.ez.no/nextgen/
>
> The layout is like
> /trunk
> /stable
> |- 4.0
> |- 3.9
> |- 3.8
> ...
> /releases
> |- 4.0
> |- 4.0r1
> |- 3.9
> |- 3.9r1
> |- 3.9r2
>
>
> I do not know, whether git-svn can create branches automatically for
> each directory under /stable and one main branch for trunk or
> whether I
> need to create one svn-remote definition for every svn directory I
> want
> to track.
I'm not sure what commands git-svn uses, but it looks like the
following command should work:
git svn clone --trunk=trunk --tags=releases --branches=stable http://pubsvn.ez.no/nextgen/
nextgen
That should create a nextgen git repository with a master branch
following SVN stable, and automatically grabbing anything under stable
or releases as a new branch. (I actually marked releases as a tag but
I think git-svn treats them as branches, since they can change on the
SVN side.)
~~ Brian
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2008-06-30 20:58 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-06-30 19:57 how does git svn work Thomas Koch
2008-06-30 20:57 ` Brian Gernhardt
-- strict thread matches above, loose matches on Subject: below --
2008-06-30 19:57 Thomas Koch
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox