I am tracking all svn commits to trunk (as well as 1.1 to make sure
they get merged to trunk) to be merged into m2migration to keep that
branch up to date with trunk.
I have been collecting them in a folder and when I get enough I SVK
merge them which is really easy.
So, I'd rather you guys just commit to trunk and if your svn ci
produces a svn commit email I will catch it and merge for you.
Only stuff that conflicts will I hold off on, but I will still track
it for resolution when we merge m2migration to trunk.
--jason
On Jul 25, 2006, at 11:13 AM, Aaron Mulder wrote:
Sure. For now, I figured it would be better to wait until the M2
thing is resolved. If I apply it to "trunk" and then we replace
"trunk" with the M2 branch I figured it might get lost. Should I
apply it to both trunk and M2 branches? Or should I rely on your SVK
procedure to catch any changes made to trunk and apply to the M2
branch?
Thanks,
Aaron
On 7/25/06, Jason Dillon <[EMAIL PROTECTED]> wrote:
Apply to trunk?
--jason
On Jul 25, 2006, at 8:57 AM, [EMAIL PROTECTED] wrote:
> Author: ammulder
> Date: Tue Jul 25 08:57:16 2006
> New Revision: 425431
>
> URL: http://svn.apache.org/viewvc?rev=425431&view=rev
> Log:
> Remove as this is really a separate tool not part of the server
> runtime environment. Plus it's not used.
>
> Removed:
> geronimo/branches/1.1/modules/system/src/java/org/apache/
> geronimo/system/util/PluginRepositoryExporter.java
>
