That would be a problem too because we would need a
StrutsMaintenanceSvnCygwin, StrutsMainenanceSvnLinux.
The notes I added are more of a guideline than a recipe.
--
James Mitchell
678.910.8017
Skpe: jmitchtx
On Nov 15, 2005, at 1:12 PM, Niall Pemberton wrote:
The only problem with these notes (and some Ted added on that page)
is that
they're unix specific and don't mean alot to me. Maybe we need a
could of
generic sections for things like this and then some additional
pages for
different environments. I use TortoiseSVN in a windoze environment and
achieving the same thing invloves "right clicking" on the tag/
branch root
directory, selecting properties from the context menu, selecting the
"subversion" tab and then editing the "svn:externals" property.
How about pages like "StrutsMaintenanceUnix" and
"StrusMaintenanceTortoiseSVN" pages for specific examples?
Niall
----- Original Message -----
From: "James Mitchell" <[EMAIL PROTECTED]>
Sent: Tuesday, November 15, 2005 5:59 PM
Let's not forget about the updates needed to support all of our uses
of svn:exterals. Whenever we branch or tag (it is really just a
copy), we'll need to fix any svn:externals to point to the tagged/
branched versions since this is not automatically done for us.
I just updated this page:
http://wiki.apache.org/struts/StrutsMaintenanceSvn
...scroll to the bottom section.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
