ns 1-3 are fine with me. Robbie, just pick the
>> easiest to execute and go for it!
>>
>> -Chuck
>>
>>
>>
>> ----- Original Message -
>>> From: "Robbie Gemmell"
>>> To: users@qpid.apache.org
>>> Sent: Monday, March 9, 20
to the stale-proton-svn trap.
>
> To be honest any of options 1-3 are fine with me. Robbie, just pick the
> easiest to execute and go for it!
>
> -Chuck
>
>
>
> - Original Message -
>> From: "Robbie Gemmell"
>> To: users@qpid.apache.org
e and go for it!
-Chuck
- Original Message -
> From: "Robbie Gemmell"
> To: users@qpid.apache.org
> Sent: Monday, March 9, 2015 12:24:43 PM
> Subject: handling old Subversion contents after migrations to Git
>
> Hi all,
>
> As you probably know, we mig
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:5
I like #2 (delete the trunk dirs and leave a README with pointers to the
git repos).
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, Robbie Gemmell wrote:
Any other thoughts out there? We seem to h
Any other thoughts out there? We seem to have a mix of responses so
far, but mostly lots of silence ;)
Robbie
On 10 March 2015 at 10:05, Robbie Gemmell wrote:
> On 9 March 2015 at 16:24, Robbie Gemmell wrote:
>> Hi all,
>>
>> As you probably know, we migrated the Proton and new JMS client code
+1 for option 3
On 9 March 2015 at 16:24, Robbie Gemmell 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.
>
>
On 9 March 2015 at 16:24, Robbie Gemmell 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.
>
> Some folks have b
+1 for option 1
-Ursprüngliche Nachricht-
Von: Robbie Gemmell [mailto:robbie.gemm...@gmail.com]
Gesendet: Montag, 9. März 2015 17:25
An: users@qpid.apache.org
Betreff: handling old Subversion contents after migrations to Git
Hi all,
As you probably know, we migrated the Proton and new
+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"
> To: users@qpid.apache.org
> Sent: Monday, March 9, 2015 12:24:43 PM
> Subject: handling old Sub
PM
> To: users@qpid.apache.org
> Subject: handling old Subversion contents after migrations to Git
>
> 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
>
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.
Some folks have been caught out by using the old stale locations, as
although we
12 matches
Mail list logo
