I think creating a branch would be best, since that will allow Gary and I to collaborate. Shall I go ahead with the copy?
- Jen On Jan 22, 2008 12:11 PM, Eric Dalquist <[EMAIL PROTECTED]> wrote: > Do you think a branch is needed for this work or can a switch be made > with a single commit? > > If a 'working' branch is needed for this do 'svn copy > https://www.ja-sig.org/svn/up2/trunk/ > https://www.ja-sig.org/svn/up2/branches/working-up3theme' and do the work > in there. I've been using http://www.orcaware.com/svn/wiki/Svnmerge.py to > manage merging changes between branches and branches back to trunk which > makes things MUCH easer than doing 'svn merge' commands. > > Thanks! > -Eric > > Jen Bourey wrote: > > Hi Eric, > > I haven't done a lot of SVN administration and haven't followed closely > how JA-SIG has been maintaining branches. Do you usually just copy the > trunk to a branch, then copy changes back into the trunk as needed? > > - Jen > > > On Jan 22, 2008 12:01 PM, Eric Dalquist <[EMAIL PROTECTED]> > wrote: > > > Gary/Jen > > > > I was just wondering if either of you were planning on doing the actual > > SVN work for switching to the new theme Gary is providing? I need to > > know to work out planning of tasks for RC2. > > > > -Eric > > > > -- > You are currently subscribed to uportal-dev@lists.ja-sig.org as: [EMAIL > PROTECTED] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/uportal-dev > > -- You are currently subscribed to uportal-dev@lists.ja-sig.org as: [EMAIL PROTECTED] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev
