Open GoogleCodeExporter opened 9 years ago
Most likely this will be migrated to GitHub, which is where a lot of the Google
Code projects are moving.
Jason, are you going to do the export? I can help with the Chromium side of
this, getting the repository address updated in the Chromium DEPS.
Original comment by andrewha...@google.com
on 7 May 2015 at 10:14
Yes, I have done this already for two other projects, and happy to do the CLD2
export within the timeline we discussed (no later than June 1).
Original comment by ri...@google.com
on 7 May 2015 at 3:08
Have poked the Chromium team on what will be required to make this move, and I
should note that the current repo is SVN based whereas GitHub (obviously) will
be Git. Anyone downstream who is mirroring our repo would need to migrate from
SVN to Git to continue receiving updates. I imagine that Git is widespread
enough at this point for that not to be a major blocker for anyone.
Original comment by andrewha...@google.com
on 7 May 2015 at 3:11
I think it will be helpful to put a notice up shortly on the project homepage
mentioning the impending move to GitHub. We'll can mention there any
implications, such as migration from SVN to Git that would be required.
Original comment by ri...@google.com
on 7 May 2015 at 3:24
The migration from svn to git isn't really required.
You can checkout as svn from github since some months (years?)
I never checked it, but you can try it yourself by clicking on subversion and
svn checkout link
"You can clone with HTTPS, SSH, or Subversion"
Original comment by costamag...@gmail.com
on 26 Jun 2015 at 7:56
github reference:
https://help.github.com/articles/support-for-subversion-clients/
BTW do you have a link? I really would like to update the Debian package to the
new code location,
thanks
Original comment by costamag...@gmail.com
on 26 Jun 2015 at 7:57
Original issue reported on code.google.com by
costamag...@gmail.com
on 6 May 2015 at 2:21