Re: [eigen] git

[Benoit Jacob <jacob.benoit.1@xxxxxxxxx>]

I'm no KDE sysadmin :)
Benoit

2009/5/2 Márton Danóczy <marton78@xxxxxxxxx>:
> hi,
>
> can you ssh into the kde svn server? If yes, you could do:
>
> svnadmin dump repos -r 669000:HEAD | svndumpfilter include
> /path/to/eigen --drop-empty-revs --renumber-revs | bzip2 |
> eigenrepos.dump.bz2
>
> with this dumpfile then you can create a repository locally and thus
> spare the kde svn server's resources.
>
> hope that helps,
> marton
>
> --
> Márton Danóczy
> Sonnenallee 55
> 12045 Berlin
> +49 176 2388 4611
> +49 30 2175 8842
>
>
>
> 2009/5/2 Gael Guennebaud <gael.guennebaud@xxxxxxxxx>:
>> another important issue to me is the ability to manage a svn mirror of
>> a hg repository. This is because I have set many svn:external to eigen
>> and I (and users who did that too) do not want to lost them.
>>
>> On Sat, May 2, 2009 at 9:01 AM, Gael Guennebaud
>> <gael.guennebaud@xxxxxxxxx> wrote:
>>> On Sat, May 2, 2009 at 3:08 AM, Benoit Jacob <jacob.benoit.1@xxxxxxxxx> wrote:
>>>> Thanks a lot for your work.
>>>>
>>>> For those who didn't follow today's irc discussion:
>>>> after orzel's work, one thing is sure, we don't have to worry about
>>>> git-svn anymore. We have basically 2 options:
>>>> - either stay with Hg
>>>> - or convert that to Git (which gael has been experimenting with).
>>>
>>> I tried two tools:
>>> - hg-to-git (http://permalink.gmane.org/gmane.comp.version-control.git/36601)
>>> - hg-fast-export
>>> (http://hedonismbot.wordpress.com/2008/10/16/hg-fast-export-convert-mercurial-repositories-to-git-repositories/)
>>>
>>> and in both cases the branches seem to have been "linearized". So I
>>> give up for the hg to git conversion, and propose to stay with hg.
>>> However, before we make a final decision I would like we establish a
>>> workflow with associated hg commands to be sure the hg way to work is
>>> ok for us (I know hg is not very flexible to that respect in contrast
>>> to bzr for instance). Since I don't know hg yet, I cannot start that
>>> right now, but I'll start learning it and fill a section of the
>>> Developer's corner wiki page.
>>>
>>> and btw, thanks a lot to Thomas for his work !
>>>
>>> cheers,
>>> gael
>>>
>>>
>>>> We'll make a decision soonish... initially i almost dismissed Hg as I
>>>> regarded it as a small, obscure project, until I learnt that it has
>>>> Python, Mozilla, OpenOffice, Java, OpenSolaris, Xine, XEmacs and some
>>>> big Google projects among its users.
>>>>
>>>> http://www.selenic.com/mercurial/wiki/ProjectsUsingMercurial
>>>>
>>>> Given that, in the special case of KDE's SVN, Hg's svn
>>>> interoperability seems much better than git's, using Hg may also make
>>>> our life easier in the short term for syncing kdesupport and,
>>>> conversely, merging commits made there.
>>>>
>>>> I'm slightly in favor of Hg now but i still don't have a strong
>>>> opinion either way...
>>>>
>>>> Benoit
>>>>
>>>> 2009/5/2 Thomas Capricelli <orzel@xxxxxxxxxxxxxxx>:
>>>>>
>>>>> Hi again,
>>>>>
>>>>> Here's another experiment, using so-called 'named branches'.
>>>>>
>>>>> http://sources.freehackers.org/hg.cgi/eigen.named/
>>>>>
>>>>> The main difference is that the output of 'hg branches' and the 'branches'
>>>>> part of the previous url now display the name of branches. Also, you can use
>>>>>        hg up -r <branchname>
>>>>> to switch  between branches.
>>>>>
>>>>> I'm often on #eigen, if you want to test eigen/mercurial and need some help,
>>>>> just ask.
>>>>>
>>>>> I think the most basic test is about cloning one of those repositories, and
>>>>> then play with 'hg view' (the tcl/tk viewer, much the same as git's one).
>>>>>
>>>>> regards,
>>>>> Thomas
>>>>>
>>>>>
>>>>>
>>>>> On Friday 01 May 2009 22:47:29 Thomas Capricelli wrote:
>>>>>> Hi all,
>>>>>>
>>>>>> I'm looking into converting the svn repository for eigen2 to mercurial. You
>>>>>> can so far follow my experiments on
>>>>>>
>>>>>> http://sources.freehackers.org/hg.cgi/eigen/
>>>>> --
>>>>> Thomas Capricelli <orzel@xxxxxxxxxxxxxxx>
>>>>> http://www.freehackers.org/thomas
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>
>>
>>
>
>
>