Ok, ok :-) . I will be moving SnS (and all my projects) to git here shortly and I also have some planned improvements for it (want to integrate support for images and import/export).

Please keep in mind that my business and related projects have kept me very busy, so read "shortly" loosely. (But I really am getting closer by the day. Really.) Thanks for your patience.

-Chris

Tim Gossett wrote:
On Mon, Oct 6, 2008 at 11:02 AM, Jay Levitt <[EMAIL PROTECTED]>wrote:

Tim Gossett wrote:

This particular problem will go away when git becomes accessible enough to
Chris Parrish, and all of the SnS extensions move to github.

So... what can we do to get Chris on git? :)

I remember he was having trouble w/being on Windows.  I've got Windows and
Mac on my Mac, and though I don't know git very well, if there's any sort of
"hey, can you replicate this" problem, I'm happy to help out.  I think git's
got linefeeds sorted out now, which was one of the bigger interoperability
problems.


I'm just spit-balling here, but I would guess the migration from SVN to git
would take these steps:

   1. git-svn clone locally
   2. gitignore .svn directories and other SVN files which are to be ignored
   3. git commit
   4. git push to github repo

I'm sure there are a few of you out there who have actually done this
before, and can provide a more detailed outline. As Sean has generously
offered, Chris can get setup on git at the Radiant Sprint Weekend (if he's
willing). For anyone else in Chris' situation, a quick guide on a wiki
somewhere would be great.

Perhaps I can be the Mohit of github for a minute here and request that
someone expand http://github.com/guides/import-from-subversion for those git
users on Windows?


_______________________________________________
Radiant mailing list
Post:   [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Reply via email to