SWF / MVC write-up
David Langenberg
davel at uchicago.edu
Fri Sep 6 16:57:28 EDT 2013
Sorry to butt in, but if you're going to undergo a huge repo reorg why not
also take the opportunity to move to Git at the same time. Seems that was
desired by some (move to Git) in the past and the amount of work require to
pop a massive svn repo into several smaller git repos while preserving
history is really not all that much. I only mention this because we're
doing the same thing here in the IAM group at Chicago -- busting one
massive repo (ours in this case stretches back to 1999 and has gone through
RCS -> CVS -> SVN -> Hg and now into smaller project-based git repos).
Dave
On Fri, Sep 6, 2013 at 1:59 PM, Brent Putman <putmanb at georgetown.edu> wrote:
>
> On 9/6/13 11:14 AM, Tom Zeller wrote:
>
> > Moving all svn projects to the top level, meaning no more utilities/
> > and extensions/, would enable the use of an Eclipse Team Project Set
> > file to set up a workspace from scratch
>
> I'm not familiar with that, sounds cool.
>
> > _and_ the scripts in the
> > parent projects could be modified once to work.
>
> Don't know what you mean, but if something doesn't work now and this
> would make it work, that would be good obviously.
>
> My only potential concern with making all new repos is: I'm a big fan
> of not losing svn history (unlike Chad). So if we were going to do
> this, IMHO we would want to do it right and make sure each new repo
> wound up with all its original history intact. So either 1) literally
> copy the utilities/extensions repos N times, and then in each delete all
> but the one that's supposed to stay, or 2) use the svn dumpfilter (?)
> stuff to filter a dump file to get just the relevant subtree, and then
> import it into a fresh repo.
> --
> To unsubscribe from this list send an email to
> dev-unsubscribe at shibboleth.net
>
--
David Langenberg
Identity & Access Management
The University of Chicago
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/dev/attachments/20130906/761e672e/attachment-0001.html
More information about the dev
mailing list