<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Greg,<br>
<br>
This makes sense to me, but FYI it will affect the build scripts in the
branches. I am going to start another thread to bring this to PSC vote.<br>
<br>
Thanks all,<br>
Bob<br>
<br>
Greg Boone wrote:
<blockquote
cite="mid4187BAA24A3D094F925AEE0BE39B70770514ED23@msgusaemb01.autodesk.com"
type="cite">
<pre wrap="">I see....
Then I propose that we have the following...
/fdo - Repository
/trunk
/fdodev
/core
/tools
/thirdparty
/utilities
/providers
/sdf
/shp
/...
/branches
/3.2.x
/fdodev
-----Original Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto:fdo-internals-bounces@lists.osgeo.org">fdo-internals-bounces@lists.osgeo.org</a>
[<a class="moz-txt-link-freetext" href="mailto:fdo-internals-bounces@lists.osgeo.org">mailto:fdo-internals-bounces@lists.osgeo.org</a>] On Behalf Of Robert Bray
Sent: Tuesday, January 16, 2007 4:05 PM
To: FDO Internals Mail List
Subject: Re: [fdo-internals] PSC: Interesting Conundrum
You need a single root for branch operations. Otherwise you will have to
branch each of those folders or have /branches/3.2.x/trunk which is
kinda weird.
Bob
Greg Boone wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Why do we you recommend the /fdodev parent directory?
Why not....
/fdo - Repository
/trunk
/fdo
/thirdparty
/utilities
/providers
/sdf
/shp
/...
-----Original Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto:fdo-internals-bounces@lists.osgeo.org">fdo-internals-bounces@lists.osgeo.org</a>
[<a class="moz-txt-link-freetext" href="mailto:fdo-internals-bounces@lists.osgeo.org">mailto:fdo-internals-bounces@lists.osgeo.org</a>] On Behalf Of Robert
</pre>
</blockquote>
<pre wrap=""><!---->Bray
</pre>
<blockquote type="cite">
<pre wrap="">Sent: Tuesday, January 16, 2007 3:11 PM
To: FDO Internals Mail List
Subject: Re: [fdo-internals] PSC: Interesting Conundrum
Ok, so the next step is figuring out what the repository should look
like. Trying to avoid as much pain as possible I'd like to propose
something like:
/fdo - Repository
/trunk
/fdodev
/fdo
/thirdparty
/utilities
/providers
/sdf
/shp
/...
/branches
/3.2.x
/fdodev
...
With some creative manipulation of the svn dumps and the --parent-dir
option of the svnadmin load command I think we can restructure things
without loss of history or anything else. The build scripts will need
</pre>
</blockquote>
<pre wrap=""><!---->a
</pre>
<blockquote type="cite">
<pre wrap="">fair bit of updating however.
Other ideas or suggestions welcome of course.
Bob
_______________________________________________
fdo-internals mailing list
<a class="moz-txt-link-abbreviated" href="mailto:fdo-internals@lists.osgeo.org">fdo-internals@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/fdo-internals">http://lists.osgeo.org/mailman/listinfo/fdo-internals</a>
_______________________________________________
fdo-internals mailing list
<a class="moz-txt-link-abbreviated" href="mailto:fdo-internals@lists.osgeo.org">fdo-internals@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/fdo-internals">http://lists.osgeo.org/mailman/listinfo/fdo-internals</a>
</pre>
</blockquote>
<pre wrap=""><!---->
_______________________________________________
fdo-internals mailing list
<a class="moz-txt-link-abbreviated" href="mailto:fdo-internals@lists.osgeo.org">fdo-internals@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/fdo-internals">http://lists.osgeo.org/mailman/listinfo/fdo-internals</a>
_______________________________________________
fdo-internals mailing list
<a class="moz-txt-link-abbreviated" href="mailto:fdo-internals@lists.osgeo.org">fdo-internals@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/fdo-internals">http://lists.osgeo.org/mailman/listinfo/fdo-internals</a>
</pre>
</blockquote>
<br>
</body>
</html>