[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Compressed Pristines (Summary)

From: Branko Čibej <brane_at_apache.org>
Date: Thu, 05 Apr 2012 18:24:37 +0200

On 05.04.2012 17:35, Ashod Nakashian wrote:
>> ________________________________
>> From: Hyrum K Wright <hyrum.wright_at_wandisco.com>
>>
>> I'm glad we've found a way to relegate this problem to a "minor...technicality."
> So far no objections then.
>
> What's the preferred mode of operation in such a case?
>
> I can update the proposal and start sending patches for the dev-list to review or I can work in a branch with post-commit reviews.

I'd like to see this happen on trunk, with the whole compressed-pristine
functionality wrapped in conditional-compilation blocks.

However, there's likely to be a lot of churn and reviewing all those
patches would never happen in real time. Therefore, I propose you do the
work on a branch, CTR of course. There should be no problem giving you
branch commit access, IMO.

-- Brane
Received on 2012-04-05 18:24:45 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.