On Sat, Sep 18, 2010 at 12:12:21PM +0000, Jens Rehsack wrote: > On 09/18/10 10:26, H.Merijn Brand wrote: > >On Sat, 18 Sep 2010 09:13:15 +0000, Jens Rehsack > ><rehs...@googlemail.com> wrote: > > > >>>(I may also move the code to github to make it easier, presumably, for > >>>others to work together on branches without affecting the mainline.) > >> > >>In that case I wouldn't continue my effort on the pure-perl DBD's etc., > >>git might be ok if there is someone who could guide me, but github isn't. > >> > >>I further don't understand what's so difficult on svn cp dbi/trunk > >>dbi/branches/foo - and a merge back after that - but this is another > >>discussion and it's probably done by others ... > > > >We really ought to have a hands-on meet-up one-day :) > > > >Then we can *show* the way we all work. > > That would be great, but I *still* don't understand why changing the tool > will solve any problem (except the old tool doesn't support some kind of > requested feature).
It wouldn't. It's simply that as I learn more git the limitations of svn become more tiresome. > Further, I don't intend to join another social network (named github) > when I don't see any advantage. It should be easy to take a simple > repository hoster - or put the repository to any host we already own > or can use. I don't think there's any need to treat github as a social network. You could also host your own repro anywhere you like with git. Anyway, I'm in no rush to change. Feel free to create branches in svn (following the normal svn naming conventions). Tim.
