Hello Luigi,
could one also do this "git filter-branch --prune-empty
--subdirectory-filter QuantLib -- --all" directly on (a copy of) one's
local repository, thus keeping *all* (local) branches, and then push
back some branches to a fresh fork of lballabio/QuantLib? This way it
would be easier to keep private branches in the local repo that should
not appear on the github repo. Or would that be unsafe for some
reason?
Thanks a lot
Peter
On 17 December 2015 at 17:55, Luigi Ballabio <[hidden email]> wrote:
> Hi all,
> Eric and I just finished splitting the QuantLib git repository in
> smaller modules. The main forks for the new, smaller repos are:
>
> QuantLib: https://github.com/lballabio/QuantLib
> QuantLib-SWIG: https://github.com/lballabio/QuantLib-SWIG
> reposit: https://github.com/eehlers/reposit
> QuantLibAddin: https://github.com/eehlers/QuantLibAddin
> QuantLibXL: https://github.com/eehlers/QuantLibXL
>
> Eric's modules refer to the new reposit build. The old build is still
> hosted at https://github.com/eehlers/quantlib for the time being.
>
> For those of you that had forked the old repository, see the instructions at
> http://quantlib.org/forkmigration.shtml for migrating any modifications you
> want to keep.
>
> Thanks for your patience,
> Luigi
>
>
>
> On Thu, Dec 10, 2015 at 5:36 PM Luigi Ballabio <[hidden email]>
> wrote:
>>
>> Hi all,
>> Eric and I will be splitting the QuantLib git repository in smaller
>> modules in the next few days (see my previous post, quoted below, for more
>> details). Once it's done, most of you that forked it on GitHub or cloned it
>> locally can probably just fork or clone again the modules you're interested
>> in. For those of you that have additional branches you want to keep, I'll be
>> posting instructions for migrating them to the new modules.
>>
>> Later,
>> Luigi
>>
>>
>> On Mon, Oct 26, 2015 at 3:09 PM Luigi Ballabio <[hidden email]>
>> wrote:
>>>
>>> [ cross-posted to quantlib-users and quantlib-dev; apologies for any
>>> duplicates. ]
>>>
>>> Hi all,
>>> I'm currently 3 or 4 issues away from setting up the 1.7 release.
>>>
>>> Shortly after doing that, and in concert with the other maintainers, I'll
>>> reorganize the Git repository so that the current, monolithic one containing
>>> all the modules will be split into smaller ones, with one module per current
>>> directory; thus, there will be a repository for the core C++ library, one
>>> for the Excel addin and so on.
>>>
>>> This will make it more convenient for the maintainers to manage the
>>> modules for which they have responsibility, and will also make it a lot
>>> easier to add new modules. We had considered doing this when we migrated
>>> from subversion to git, and in hindsight we should have gone ahead at that
>>> time.
>>>
>>> I'm aware this will cause inconveniences to the 500+ people that forked
>>> the repository on GitHub. I am sorry for this, and I will try to minimize
>>> the pain: I'll migrate the open pull requests to the new repository, and
>>> I'll try to make some kind of guide to help those of you with local changes
>>> to move them to the new fork. In the meantime, your current forks are not
>>> going away.
>>>
>>> Thanks for the understanding. I'll post a timeline as soon as I have one.
>>>
>>> Luigi
>>>
>>> --
>>>
>>> <http://leanpub.com/implementingquantlib>
>>> <http://implementingquantlib.com>
>>> <http://twitter.com/lballabio>
>>
>> --
>>
>> <http://leanpub.com/implementingquantlib>
>> <http://implementingquantlib.com>
>> <http://twitter.com/lballabio>
>
> --
>
> <http://leanpub.com/implementingquantlib>
> <http://implementingquantlib.com>
> <http://twitter.com/lballabio>
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> QuantLib-dev mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/quantlib-dev
>
<http://leanpub.com/implementingquantlib>
<http://implementingquantlib.com>
<http://twitter.com/lballabio>
| Free forum by Nabble | Disable Popup Ads | Edit this page |