For Ferry, The workflow to apply github pull requests with git svn is complex and error prone. More and more, contributions from the outside come in as pull requests.
What's 'broken', and I choose that term with some trepidation, is that some of us really prefer some git workflow (task branches, whatever), and use git at our day jobs, and would rather not switch our brains to svn or the combination. The premise of this discussion is that if we're willing to do the work, others are willing to see us do it. It could be that there isn't a consensus for that. On Tue, Oct 27, 2015 at 6:22 AM, Ferry Huberts <maili...@hupie.com> wrote: > Side-line for me too. > > How about just using 'git svn ...' > > Work locally in git, store in svn. > What's the big deal? > > If there are blocking process issues _then_ you switch, right? > > > > > On 27/10/15 11:16, Achim Nierbeck wrote: >> >> Just looking from the side-line of this ... >> ... but all of this sounds more like a lot of pain compared to the gain. >> >> SVN isn't that bad after all, so why fix something that isn't really >> broken? >> Right now I don't see much of a benefit to this, but as I'm not part of >> any >> decision makers here, >> take this just as a little hint :-) >> >> regards, Achim >> >> >> 2015-10-27 11:12 GMT+01:00 Benson Margulies <bimargul...@gmail.com>: >> >>> My recommendation at this point in the discussion is to convert the >>> repo _en bloc_, then split out very independent things (if any), and >>> only then contemplate add-ons. >>> >> >> >> > > -- > Ferry Huberts
