Subject: Re: [boost] [git] Near future.. How do we deal with git-native libraries?
From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2014-01-04 16:24:23
On Sat, Jan 4, 2014 at 2:41 PM, Daniel James <daniel_at_[hidden]> wrote:
> On 4 January 2014 14:34, Beman Dawes <bdawes_at_[hidden]> wrote:
> > On Thu, Jan 2, 2014 at 10:58 PM, Rene Rivera <grafikrobot_at_[hidden]>
> >> Thanks Daniel for the procedure.. I mostly followed it (I had after the
> >> fact created a develop branch so both replacements steps where the same)
> >> and it seems to have worked. Just waiting to see if the super commit bot
> >> will update to the new branches.
> > I've captured Daniel's procedure at
> > https://svn.boost.org/trac/boost/wiki/NewLibFromGit
> > Comments and corrections appreciated.
> It isn't appropriate for new libraries. It's just for a library that
> was in subversion, but was really using git already. I think the only
> examples are predef and odeint. We should sort out odeint very soon.
A similar procedure could be appropriate if the branches that the project
has are not the ones mandated by Boost. But, otherwise it's for libraries
with both SVN and GIT histories. For new ones it looks like there's a
simpler github option to just transfer ownership of the repo directly from
one user to another.
-- -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk