Err, actually, now that I think of it, we use svn:externals locally against the JASIG svn repository, and locally we would remain using svn because that's the university's repository. I'd probably end up scripting the git commands for our build process. Then I'd use git commands if I were working on a patch for a community portlet.
This isn't a 4:30pm puzzle. On Wed, Aug 31, 2011 at 4:29 PM, Bruce Tong <[email protected]> wrote: > There's a command line interface, cool. > > Does git have anything like svn:externals? A quick search brought up a > few pages that lead me to believe it might be an issue, though if a > read-only SVN repository is still part of the plan, maybe that covers > it. I'd have to do more research. > > On Wed, Aug 31, 2011 at 3:26 PM, Eric Dalquist > <[email protected]> wrote: >> Some questions that I can try and answer before they come up: >> - The uPortal code in svn at source.jasig.org would likely be left in place, >> we would just make the entire /uPortal directory read-only >> - We're going to filter out the documentation and website files that were >> included in early versions of uPortal 2 to reduce the project repository >> size. >> >> Since this is a big change (and since I'm going on vacation for 2 weeks >> starting Friday) I'm planning on leaving this vote open for a while. +1, 0, >> -1 to vote and if you vote -1 you need to include a detailed reasoning for >> your -1 vote. >> >> -Eric >> > > > > -- > Bruce Tong > Software Engineer > Office of Information Technology > Ohio University > -- Bruce Tong Software Engineer Office of Information Technology Ohio University -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev
