[mapguide-internals] Initial review on RFC90 - Need help with repo actions

Tom Fukushima tom.fukushima at autodesk.com
Mon Jun 6 13:25:28 EDT 2011


OK, I created rfc90.2 in the sandbox and left the existing one there as rfc90.

Tom

-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Tom Fukushima
Sent: Monday, June 06, 2011 9:29 AM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] Initial review on RFC90 - Need help with repo actions

I can look into this if no one else is.

-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Zac Spitzer
Sent: Monday, June 06, 2011 7:13 AM
To: MapGuide Internals Mail List
Subject: Re: [mapguide-internals] Initial review on RFC90 - Need help with repo actions

can someone with svn rights action this request?

On Sat, Jun 4, 2011 at 2:07 AM, UV <uvwild at googlemail.com> wrote:
> Hello MG internal team,
>
> I would like to finalize the rfc90 submission.
> However, my code changes are ridiculously small compared to the trunk 
> changes since I started with rfc90.
> As well I recently failed to remotely merge the trunk back into the
> rfc90 feature branch (probably due to resource limitations)
>
> Please, could someone sitting close to the repository either
> a) delete rfc90 branch and create a new branch from trunk
> b) or create a new branch called e.g. metatiling from trunk and 
> provide access to them for me?
>
> The generaly functionality of the rfc90 contribution is basicallly 
> finished since a year.
> But the simple refactoring of the code to fulfill the reviewers 
> requests turned into 95% merge and setup and 5% writing code.
> (including many long hours of repo actions) due to the long breaks I had to take.
>
> So to finish this with minimal effort I would like to locally merge my 
> few changes into a new branch which then can be hopefully reviewed 
> quickly and merged back into the trunk. This should cut down the work considerably.
>  Alternatively I create a patch for trunk, however, such a patch 
> against trunk is also a moving target and therefore not the best solution.
>
> Thank you for your support.
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>



--
Zac Spitzer
Solution Architect / Director
Ennoble Consultancy Australia
http://www.ennoble.com.au
http://zacster.blogspot.com
+61 405 847 168
_______________________________________________
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-internals


More information about the mapguide-internals mailing list