Re: [eigen] git

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

Arf, they say hgsubversion is still alpha quality and the alternatives
seem cumbersome.

Here's another approach, since you don't need the svn copy of eigen to
remember history:

Just export eigen2 from hg (as if you wanted to create a tarball) and
then use only svn to push that online.

2009/5/2 Benoit Jacob <jacob.benoit.1@xxxxxxxxx>:
> Does this help?
> http://www.selenic.com/mercurial/wiki/index.cgi/WorkingWithSubversion
>
> Quote:
> When you want to push the changes directly into svn, you first pull
> the latest changes from svn, then rebase your changes to the svn HEAD
> and push them back.
>
> $ hg svn pull # pull the changes from svn
> $ hg up your_head # update the repo to the head of the changes you
> want to push to svn
> $ hg svn rebase # rebase your_head onto svn
> $ hg svn push
>
>
> 2009/5/2 Gael Guennebaud <gael.guennebaud@xxxxxxxxx>:
>> well that depends what you mean by "manual", if it is only one or two
>> commands to run whenever we want to sync it's ok, but if you have to
>> do the svn add manually, or so then that's another story.  So, yes,
>> basically I still don't see how to do it easily....
>>
>> On Sat, May 2, 2009 at 4:01 PM, Benoit Jacob <jacob.benoit.1@xxxxxxxxx> wrote:
>>> Syncing it manually will sure be easy; isn't it better anyway? So your
>>> users aren't affected by every change made in the development branch?
>>>
>>> Benoit
>>>
>>> 2009/5/2 Gael Guennebaud <gael.guennebaud@xxxxxxxxx>:
>>>> sure, my problem was not to have a svn repository (I have many
>>>> possibilities for that), but how easy is it to keep a svn mirror sync
>>>> from hg ?
>>>>
>>>> On Sat, May 2, 2009 at 3:52 PM, Benoit Jacob <jacob.benoit.1@xxxxxxxxx> wrote:
>>>>> Gael: I have an idea for you.
>>>>>
>>>>> Even after we've removed eigen from kdesupport, we may perfectly keep
>>>>> it in some SVN somewhere -- so that it's still possible to do
>>>>> svn:externals. You'd then sync that svn copy whenever you want.
>>>>>
>>>>> The simplest thing would be to ask tuxfamily to create a svn
>>>>> repository for us. I know i already used tuxfamily's svn server and it
>>>>> is very fast.
>>>>>
>>>>> Cheers,
>>>>> Benoit
>>>>>
>>>>> 2009/5/2 Benoit Jacob <jacob.benoit.1@xxxxxxxxx>:
>>>>>> Short term, yes, and gael can update kdesupport as often as he needs to.
>>>>>>
>>>>>> Long term, we're back to the old discussion "kdesupport is not a
>>>>>> dumping ground for copies of external libraries" so we'll drop
>>>>>> kdesupport after a few monthes.
>>>>>>
>>>>>> Benoit
>>>>>>
>>>>>> 2009/5/2 Thomas Capricelli <orzel@xxxxxxxxxxxxxxx>:
>>>>>>>
>>>>>>> Oh, ok, I see. So all need to be done is to have the eigen directory in
>>>>>>> kdesupport updated often enough with respect to the dvcs one ? This is
>>>>>>> possible.
>>>>>>>
>>>>>>> Thomas
>>>>>>>
>>>>>>>
>>>>>>> On Saturday 02 May 2009 15:35:02 Benoit Jacob wrote:
>>>>>>>> No, he means svn:external's in other non-KDE project.
>>>>>>>>
>>>>>>>> kdesupport will keep a plain copy of eigen in the short term, not a
>>>>>>>> svn:external.
>>>>>>>
>>>>>>> --
>>>>>>> Thomas Capricelli <orzel@xxxxxxxxxxxxxxx>
>>>>>>> http://www.freehackers.org/thomas
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>>
>