[Opensim-dev] [Opensim-users] Main Repository now in Git

[Sean Hennessee]

In my automated update script I use an svn info command to cull the 
current release number to use as it's folder name when getting the 
latest release like this:

$ REV=`svn info http://opensimulator.org/svn/opensim/trunk | fgrep 
Revision | awk '{print $2}'`
$ svn -r $REV co http://opensimulator.org/svn/opensim/trunk $REV

With the specific svn command used being:
$ svn info http://opensimulator.org/svn/opensim/trunk
Is there an equivalent way to get the current release number from git? 
Or any way to get the current/trunk release number?

Google was not my friend this morning:
"$ git remote show origin" gives a lot of info, but I can't tell which 
of that info is the latest release available. "git remote -v" only seems 
to show the git:// source of a local repository. "git svn info" is 
giving me this error: "Can't locate SVN/Core.pm in @INC <...>".

Peace,
Sean


Sean Dague wrote:
> We've now transitioned the main active source repository to git, all the
> documentation is not yet updated, but there is a basic document on using
> git at http://opensimulator.org/wiki/Using_Git.  Over the next week the
> rest of the wiki should be cleaned up to match that.
> 
> In order to provide minimal impact on our user base there is now a new
> subversion mirror of the git working repository.  That can be checked
> out with: svn co http://opensimulator.org/svn/opensim-track/trunk.  It
> is a changeset by changeset tracking repo on unstable upstream git for
> opensim (it may be delayed by up to 15 minutes, but will contain all the
> same content).  It starts mirroring at version 10001.
> 
> The existing http://opensimulator.org/svn/opensim svn will no longer be
> getting any commits.  If you would like to continue using svn for
> anonymous checkout of trunk, please switch to the opensim-track repository.
> 
> Users are encouraged to explore using git.  One of the reasons for the
> switch is that it makes it easier for our non core contributors to
> contribute more complex code, as everyone gets to use an equivalent
> toolchain, core or not.
> 
> There will probably be a few more bumps along the road, but the
> transition today went relatively smoothly.  Questions are always
> welcomed as we come through the transition.
> 
> 	-Sean

-- 

Sean Hennessee
Central Computing Support
Information and Academic Technologies
UC Irvine


... . .- -. /  .... . -. -. . ... ... . .