The last SVN update is indeed r2272, committed 2009-08-10 10:10:24 -0700 today. The SVN repository is up to date and is the master copy of the project.

Several people (including me) work a lot offline and commit after, to not break the main branch. Some of them use git-svn :-)

HTH,
Laurent

On Aug 10, 2009, at 6:29 PM, Conrad Taylor wrote:

Matt, I asked the question because I noticed that there hasn't been any updates to the SVN repository. At this time, I'm at revision 2272. Is this correct?

-Conrad

On Mon, Aug 10, 2009 at 6:19 PM, Matt Aimonetti <mattaimone...@gmail.com > wrote: The official repository is on SVN but a few of us use git-svn to work on our branches and commit back to SVN.

If you are planning on contributing patches, whatever SCM you want to use is fine as long as your patches apply fine on the svn repo.

If you wish to switch to git-svn, see the discussion we recently had about the best process. (It's a thread started by Patrick letting people know about the work he did on the YAML rewrite and I went OT asking Eloy and others about git-svn.)

Good luck,

- Matt



On Mon, Aug 10, 2009 at 6:10 PM, Conrad Taylor <conra...@gmail.com> wrote: Hi, I was wondering, are we using Git or Subversion these days? If we're switching to Git, how does one migrate to it from an existing SVN repository.

Thanks,

-Conrad





_______________________________________________
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel



_______________________________________________
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


_______________________________________________
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

_______________________________________________
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Reply via email to