[GitHelp] odeints repository
Hi, odeint has already a git repository at github (https://github.com/headmyshoulder/odeint-v2). Can this be used instead of the default boost git repository for odeint? At the moment the directory structure of this repository uses the old structure odeint odeint/boost odeint/boost/numeric/ odeint/boost/numeric/odeint odeint/libs/numeric odeint/libs/numeric/odeint odeint/libs/numeric/odeint/doc odeint/libs/numeric/odeint/test but it can easily be changed to fit to the new directory structure.
2013/1/1 Karsten Ahnert <karsten.ahnert@googlemail.com>:
Hi,
odeint has already a git repository at github (https://github.com/headmyshoulder/odeint-v2). Can this be used instead of the default boost git repository for odeint?
Of course!
At the moment the directory structure of this repository uses the old structure
odeint odeint/boost odeint/boost/numeric/ odeint/boost/numeric/odeint odeint/libs/numeric odeint/libs/numeric/odeint odeint/libs/numeric/odeint/doc odeint/libs/numeric/odeint/test
but it can easily be changed to fit to the new directory structure.
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
On 01/01/2013 10:07 PM, Daniel Pfeifer wrote:
2013/1/1 Karsten Ahnert <karsten.ahnert@googlemail.com>:
Hi,
odeint has already a git repository at github (https://github.com/headmyshoulder/odeint-v2). Can this be used instead of the default boost git repository for odeint?
Of course!
Ohh, that's cool. What do we have to do to switch the existing repository? Of course, the first step for us is to change the existing directory structure.
on Tue Jan 01 2013, Karsten Ahnert <karsten.ahnert-AT-googlemail.com> wrote:
On 01/01/2013 10:07 PM, Daniel Pfeifer wrote:
2013/1/1 Karsten Ahnert <karsten.ahnert@googlemail.com>:
Hi,
odeint has already a git repository at github (https://github.com/headmyshoulder/odeint-v2). Can this be used instead of the default boost git repository for odeint?
Of course!
Ohh, that's cool. What do we have to do to switch the existing repository? Of course, the first step for us is to change the existing directory structure.
Wait, wait, wait a sec. You can use that repository for whatever purpose you like, but at least initially, the Boost organization will still have its own public odeint repo from which it does Boost releases. The odeint maintainers will of course have write privileges on that repo. -- Dave Abrahams BoostPro Computing Software Development Training http://www.boostpro.com Clang/LLVM/EDG Compilers C++ Boost
On 2 January 2013 10:22, Dave Abrahams <dave@boostpro.com> wrote:
Wait, wait, wait a sec. You can use that repository for whatever purpose you like, but at least initially, the Boost organization will still have its own public odeint repo from which it does Boost releases.
Surely the public repo can be based on the existing odeint repo.
on Wed Jan 02 2013, Daniel James <dnljms-AT-gmail.com> wrote:
On 2 January 2013 10:22, Dave Abrahams <dave@boostpro.com> wrote:
Wait, wait, wait a sec. You can use that repository for whatever purpose you like, but at least initially, the Boost organization will still have its own public odeint repo from which it does Boost releases.
Surely the public repo can be based on the existing odeint repo.
Absolutely. -- Dave Abrahams BoostPro Computing Software Development Training http://www.boostpro.com Clang/LLVM/EDG Compilers C++ Boost
odeint has already a git repository at github (https://github.com/headmyshoulder/odeint-v2). Can this be used instead of the default boost git repository for odeint?
Of course!
Ohh, that's cool. What do we have to do to switch the existing repository? Of course, the first step for us is to change the existing directory structure.
Wait, wait, wait a sec. You can use that repository for whatever purpose you like, but at least initially, the Boost organization will still have its own public odeint repo from which it does Boost releases. The odeint maintainers will of course have write privileges on that repo.
Ok. Does that mean that we have two repositories for odeint, and we simply use the repository from Boost only for releases?
2013/1/2 Karsten Ahnert <karsten.ahnert@googlemail.com>:
odeint has already a git repository at github (https://github.com/headmyshoulder/odeint-v2). Can this be used instead of the default boost git repository for odeint?
Of course!
Ohh, that's cool. What do we have to do to switch the existing repository? Of course, the first step for us is to change the existing directory structure.
Wait, wait, wait a sec. You can use that repository for whatever purpose you like, but at least initially, the Boost organization will still have its own public odeint repo from which it does Boost releases. The odeint maintainers will of course have write privileges on that repo.
Ok. Does that mean that we have two repositories for odeint, and we simply use the repository from Boost only for releases?
Whether you use the repository from Boost for releases *only* is up to you. But yes, that is the repository that will be taken into account when Boost is released as a whole. -- Daniel
On 01/02/2013 04:47 PM, Daniel Pfeifer wrote:
2013/1/2 Karsten Ahnert <karsten.ahnert@googlemail.com>:
odeint has already a git repository at github (https://github.com/headmyshoulder/odeint-v2). Can this be used instead of the default boost git repository for odeint?
Of course!
Ohh, that's cool. What do we have to do to switch the existing repository? Of course, the first step for us is to change the existing directory structure.
Wait, wait, wait a sec. You can use that repository for whatever purpose you like, but at least initially, the Boost organization will still have its own public odeint repo from which it does Boost releases. The odeint maintainers will of course have write privileges on that repo.
Ok. Does that mean that we have two repositories for odeint, and we simply use the repository from Boost only for releases?
Whether you use the repository from Boost for releases *only* is up to you. But yes, that is the repository that will be taken into account when Boost is released as a whole.
Ahh, I've got it. Seem reasonable to me and the workflow should also be quite easy for us.
participants (4)
-
Daniel James -
Daniel Pfeifer -
Dave Abrahams -
Karsten Ahnert