I am actually just in the process of switching to this setup as well, one
repo, rather than multiple per branch. The reason being to be able to use
cherry picking. I find the git svn clone very tricky as well. It seems that
it can easily error out depending on what revision you a referencing ...
the revision that tags and branches are created on seem to fail... a few
revisions back leads to success... it is weird.

Anyways, what I hope to do (currently doing for geoserver but happy to do
it for geotools as well) is actually push this new clone into the geoserver
github account:

  https://github.com/geoserver

At the same time I plan to setup a hudson job that will do a regular svn
rebase whenever changes in svn occur.

An open question is how far back in history to go... as Andrea said full
revision history leads to a massive repo. I am tempted to just go back far
enough to pull in the latest stable branch, since we still have an svn repo
it is not crucial to have all the history.

Thoughts? I can do the same for geotools if folks are interested. This
could perhaps be the "official" repo for developers to fork locally? Would
be nice to have a single repo to share for pulling changes back and forth.

On Thu, Nov 10, 2011 at 12:35 AM, Andrea Aime
<andrea.a...@geo-solutions.it>wrote:

> On Thu, Nov 10, 2011 at 5:41 AM, Michael Bedward
> <michael.bedw...@gmail.com> wrote:
> > Dear Git users,
> >
> > I have finally started using Git, some years after most others here. I
> > must say that I like it, or at least most of it, and can see how the
> > ease of working with branches is ideal when experimenting with new
> > code in a big complex project like GeoTools. However, I'm much less
> > enthusiastic about git-svn.  I've experimented with "git svn clone -r
> > N" to clone trunk, but didn't like the endless warnings messages or
> > the sluggish speed on my modest internet line. I also note the
> > numerous queries and complaints on StackOverflow and other forums
> > about git-svn problems when working with large repos.
>
> I always get nuts when I try to do a clone of a svn repo, it seems every
> time
> I have to try 3-5 times with different options before getting the command
> right,
> (and lazy me I never write down what that was it seems...)
>
> Anyways, I'm happy with git-svn past that point and I normally use a single
> checkout switching branches as I go.
> My checkout has a not so shallow history, goes back two years (r34165) and
> has full remote svn branch references as well.
> I guess I could deep copy it, remove all the local branches containing
> experiemnts,
> tar.bz2 it and make it available as a starting point for others?
> The current checkout, including the .git folder, is 650MB, compressing it
> it should go down to a much more manageable size.
> Afaik the .git folder does not contain passwords and the like, but I may
> be wrong. Anybody knows better?
>
> Cheers
> Andrea
>
>
> --
> -------------------------------------------------------
> Ing. Andrea Aime
> GeoSolutions S.A.S.
> Tech lead
>
> Via Poggio alle Viti 1187
> 55054  Massarosa (LU)
> Italy
>
> phone: +39 0584 962313
> fax:      +39 0584 962313
>
> http://www.geo-solutions.it
> http://geo-solutions.blogspot.com/
> http://www.youtube.com/user/GeoSolutionsIT
> http://www.linkedin.com/in/andreaaime
> http://twitter.com/geowolf
>
> -------------------------------------------------------
>
>
> ------------------------------------------------------------------------------
> RSA(R) Conference 2012
> Save $700 by Nov 18
> Register now
> http://p.sf.net/sfu/rsa-sfdev2dev1
> _______________________________________________
> Geotools-devel mailing list
> Geotools-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>



-- 
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to