Hi, Thanks for the pointer. Your right, not github <-> svn, only github <-> git-dual so we would need to migrate.... and if there is a merge conflict then you have to go in and fix manually before more commits can be accepted. It might only work well if we moved entirely to Git, used GitHub as the commit server and git-dual as the official record hosted on Apache infra. That is a major change that would need much more consideration.
Since when there is a merge conflict manual intervention is required, it doesn't have many benefits over running git-svn locally and continuing to rebase. For those reasons, I'll retract the suggestion. Now we have an archive of the discussion. Best Regards Ian On 23 March 2016 at 05:55, Konrad Windszus <[email protected]> wrote: > AFAIK this does only allow bridging between Github and Apache Git ( > http://mail-archives.apache.org/mod_mbox/whimsical-dev/201602.mbox/%[email protected]%3E > ). > Not between SVN and Github. So to leverage that, Sling first has to > migrate from SVN to Git. > Konrad > > > On 22 Mar 2016, at 21:59, Ian Boston <[email protected]> wrote: > > > > On 22 March 2016 at 20:26, Robert Munteanu <[email protected]> wrote: > > > >> On Tue, 2016-03-22 at 17:48 +0000, Ian Boston wrote: > >>> Hi, > >>> Have we discussed adding Sling to the list of projects here [1] ? > >>> Best Regards > >>> Ian > >>> > >>> 1 https://git-dual.apache.org/repos/asf > >> > >> What is git-dual? > >> > > Hi, > > try > > https://git-dual.apache.org/ it explains. > > > > (Bidirectional sync between GitHub and SVN). > > > > Best Regards > > Ian > > > > > > > >> Robert > >> > >
