On 19 Jul, 16:38, Konstantin Khomoutov wrote:
> Well, let me just demonstrate a session involving `git svn` and `git
> subtree` which I recorded minutes ago (Debian Lenny, stock Git 1.6.5,
> Subversion 1.5.1):http://pastebin.com/xm8aKje4
Hi, thank you very much. I tried following the session but
On Jul 19, 6:06 pm, frankie wrote:
> > > > > Hi. I have some svn projects I want to join in a git big project.
> > > I guess I need to tell git subtree this is a svn subtree but I just
> > > don't know how.
> > Note that any Git repo can be cloned; local repositories residing on
> > your local fi
On 15 Jul, 16:44, Konstantin Khomoutov wrote:
> > > > Hi. I have some svn projects I want to join in a git big project.
> >
> > I guess I need to tell git subtree this is a svn subtree but I just
> > don't know how.
>
> Note that any Git repo can be cloned; local repositories residing on
> your lo
> > > Hi. I have some svn projects I want to join in a git big project.
> > Assuming you want to do the latter, I think git-subtree [1] can be of
> > help: as I understand, it allows you to "inject" a subtree to a bigger
> > project.
>
> Hi. I am unable to import a svn tree inside git using subtree
On 12 Jul, 16:25, Konstantin Khomoutov wrote:
> On Jul 12, 12:10 pm, frankie wrote:
>
> > Hi. I have some svn projects I want to join in a git big project.
> Assuming you want to do the latter, I think git-subtree [1] can be of
> help: as I understand, it allows you to "inject" a subtree to a b
On 12 Jul, 16:25, Konstantin Khomoutov wrote:
> On Jul 12, 12:10 pm, frankie wrote:
>
>> I have some svn projects I want to join in a git big project.
> Assuming you want to do the latter, I think git-subtree [1] can be of
> help: as I understand, it allows you to "inject" a subtree to a bigger
On Jul 12, 12:10 pm, frankie wrote:
> Hi. I have some svn projects I want to join in a git big project.
>
> I've been trying with guidelines from the git faq and from
> http://www.jonmaddox.com/2008/03/05/cleanly-migrate-your-subversion-r...
> but I'm not able to do it.
>
> So I have a new git p