Re: handling old Subversion contents after migrations to Git

2015-04-22 Thread Robbie Gemmell
Pointer files added via http://svn.apache.org/r1675435 On 18 April 2015 at 12:57, Robbie Gemmell robbie.gemm...@gmail.com wrote: Thanks for the reminder Chuck. I had meant to get to this when I was on vacation last month, but some things happened and I forgot all about it. I raised

Re: handling old Subversion contents after migrations to Git

2015-04-18 Thread Robbie Gemmell
Thanks for the reminder Chuck. I had meant to get to this when I was on vacation last month, but some things happened and I forgot all about it. I raised https://issues.apache.org/jira/browse/INFRA-9471 to request they add pointer files, and attached some patches they can use to do so. Robbie

Re: handling old Subversion contents after migrations to Git

2015-04-17 Thread Chuck Rolke
Here's the score: Option 1 2 3 4 -------- SH 0 0 1-1 CR 1 0 0-1 EA 1 0 0 0 RG 1 0 0 0 OR 0 0 1 0 TR 0 1 0 0 AC 0 1 0 0 ====

Re: handling old Subversion contents after migrations to Git

2015-03-19 Thread Alan Conway
On Tue, 2015-03-17 at 14:10 -0400, Ted Ross wrote: I like #2 (delete the trunk dirs and leave a README with pointers to the git repos). +1 This will eliminate the possibility that someone will use old code or think that the project has been abandoned. -Ted On 03/17/2015 01:58 PM,

Re: handling old Subversion contents after migrations to Git

2015-03-10 Thread Robbie Gemmell
On 9 March 2015 at 16:24, Robbie Gemmell robbie.gemm...@gmail.com wrote: Hi all, As you probably know, we migrated the Proton and new JMS client code to Git repositories last year. As part of the process the old locations within the Subversion repo were frozen read-only and left in place.

Re: handling old Subversion contents after migrations to Git

2015-03-10 Thread Oleksandr Rudyy
+1 for option 3 On 9 March 2015 at 16:24, Robbie Gemmell robbie.gemm...@gmail.com wrote: Hi all, As you probably know, we migrated the Proton and new JMS client code to Git repositories last year. As part of the process the old locations within the Subversion repo were frozen read-only and

RE: handling old Subversion contents after migrations to Git

2015-03-09 Thread Steve Huston
The only one I'm strongly opposed to is #4. I slightly prefer #3 of the remaining options. It gets the old content out of the way without deleting it. -Original Message- From: Robbie Gemmell [mailto:robbie.gemm...@gmail.com] Sent: Monday, March 09, 2015 12:25 PM To:

Re: handling old Subversion contents after migrations to Git

2015-03-09 Thread Chuck Rolke
+1 for Option 1 +0 for Option 3 -1 for Option 2 -2 for Option 4 -2 for No Change Thanks for addressing this issue. - Original Message - From: Robbie Gemmell robbie.gemm...@gmail.com To: users@qpid.apache.org Sent: Monday, March 9, 2015 12:24:43 PM Subject: handling old Subversion