Re: Subversion 1.8 httpd.exe taking 100% CPU

2013-12-11 Thread Mark Phippard
On Wed, Dec 11, 2013 at 12:28 AM, Ben Reser b...@reser.org wrote: On 8/20/13 3:15 AM, Ivan Zhakov wrote: But from what I see process is stuck in libaprutil-1.dll!7489fc50(), given the last message in debug log is auth_ldap authenticate: using URL it most likely problem with

RE: Update-Only Checkout Enhancement

2013-12-11 Thread Mark Kneisler
Yes, I understand the export function. I want functionality for release management into test and production environments. For these environments I have a few requirements: Files in these environments will NEVER be edited For new releases I will need to perform an update to

Re: Update-Only Checkout Enhancement

2013-12-11 Thread Mark Phippard
On Wed, Dec 11, 2013 at 10:46 AM, Mark Kneisler mark.kneis...@tceq.texas.gov wrote: Yes, I understand the export function. I want functionality for release management into test and production environments. For these environments I have a few requirements: Files in these

Re: Update-Only Checkout Enhancement

2013-12-11 Thread Philip Martin
Mark Kneisler mark.kneis...@tceq.texas.gov writes: Yes, I understand the export function. I want functionality for release management into test and production environments. For these environments I have a few requirements: Files in these environments will NEVER be edited For

RE: Update-Only Checkout Enhancement

2013-12-11 Thread Mark Kneisler
I think making the pristine files optional would work for me. Here's an idea. Instead of having pristine copies of all files, how about adding to the pristine directory only when a file is changed? From: Mark Phippard [mailto:markp...@gmail.com] Sent: Wednesday, December 11, 2013 9:58 AM To:

Re: Update-Only Checkout Enhancement

2013-12-11 Thread Ben Reser
On 12/11/13 7:46 AM, Mark Kneisler wrote: Yes, I understand the export function. I want functionality for release management into test and production environments. For these environments I have a few requirements: Files in these environments will NEVER be edited For new

RE: Update-Only Checkout Enhancement

2013-12-11 Thread Bob Archer
Yes, I understand the export function. I want functionality for release management into test and production environments. For these environments I have a few requirements: Files in these environments will NEVER be edited For new releases I will need to perform an update to

Re: Update-Only Checkout Enhancement

2013-12-11 Thread Les Mikesell
On Wed, Dec 11, 2013 at 11:16 AM, Bob Archer bob.arc...@amsi.com wrote: Yes, I understand the export function. I want functionality for release management into test and production environments. For these environments I have a few requirements: Files in these environments will NEVER be

Re: Update-Only Checkout Enhancement

2013-12-11 Thread Ben Reser
On 12/11/13 9:47 AM, Les Mikesell wrote: Within reasonable limits it doesn't cost anything more to send more network traffic. But the cost of client disks scales up by the number of clients. Sometimes you can get by mounting a network disk into all the clients, but then performance

Re: Update-Only Checkout Enhancement

2013-12-11 Thread Branko Čibej
On 11.12.2013 17:21, Mark Kneisler wrote: I think making the pristine files optional would work for me. Here’s an idea. Instead of having pristine copies of all files, how about adding to the pristine directory only when a file is changed? You know, that's a great idea! I wonder

RE: Update-Only Checkout Enhancement

2013-12-11 Thread Bob Archer
On 11.12.2013 17:21, Mark Kneisler wrote: I think making the pristine files optional would work for me. Here’s an idea. Instead of having pristine copies of all files, how about adding to the pristine directory only when a file is changed? You know, that's a great idea!

Re: Update-Only Checkout Enhancement

2013-12-11 Thread Branko Čibej
On 11.12.2013 20:19, Bob Archer wrote: On 11.12.2013 17:21, Mark Kneisler wrote: I think making the pristine files optional would work for me. Here’s an idea. Instead of having pristine copies of all files, how about adding to the pristine directory only when a file is changed? You

RE: Update-Only Checkout Enhancement

2013-12-11 Thread Bob Archer
On 11.12.2013 20:19, Bob Archer wrote: On 11.12.2013 17:21, Mark Kneisler wrote: I think making the pristine files optional would work for me. Here’s an idea. Instead of having pristine copies of all files, how about adding to the pristine directory only when a file is

Re: Update-Only Checkout Enhancement

2013-12-11 Thread Warren Block
On Wed, 11 Dec 2013, Les Mikesell wrote: On Wed, Dec 11, 2013 at 11:16 AM, Bob Archer bob.arc...@amsi.com wrote: Yes, I understand the export function. I want functionality for release management into test and production environments. For these environments I have a few requirements:

Re: Update-Only Checkout Enhancement

2013-12-11 Thread Les Mikesell
On Wed, Dec 11, 2013 at 12:24 PM, Ben Reser b...@reser.org wrote: On 12/11/13 9:47 AM, Les Mikesell wrote: Within reasonable limits it doesn't cost anything more to send more network traffic. But the cost of client disks scales up by the number of clients. Sometimes you can get by mounting

Re: Update-Only Checkout Enhancement

2013-12-11 Thread Les Mikesell
On Wed, Dec 11, 2013 at 3:05 PM, Bob Archer bob.arc...@amsi.com wrote: Wouldn't that mean that you need to have some daemon service (or file watcher or something) running to determine if a file is modified? Yes. Why would you need that in real-time instead of only when an svn operation is

Re: Update-Only Checkout Enhancement

2013-12-11 Thread Ben Reser
On 12/11/13 5:10 PM, Les Mikesell wrote: Not exactly. Network traffic is generally bursty. Clients rarely spend 100% of their time checking out files, so a very large number could share a local network even if they always deleted their workspaces and checked out fresh copies. But when

Re: Update-Only Checkout Enhancement

2013-12-11 Thread Les Mikesell
On Wed, Dec 11, 2013 at 8:26 PM, Ben Reser b...@reser.org wrote: Absolutely, the answer here isn't a one size fits all. Nobody is objecting to the idea of allowing this. The problem is that the code is not designed to allow this and it's a ton of work to change that. I can think of a good

Re: Update-Only Checkout Enhancement

2013-12-11 Thread Ryan Schmidt
On Dec 11, 2013, at 19:19, Les Mikesell wrote: Also, it would mean you would need a constant connection to the server to use a subversion working copy. That's hardly a problem these days, You apparently don’t try to work at the kinds of coffee shops I go to, where 50 college students are

Re: Update-Only Checkout Enhancement

2013-12-11 Thread Ben Reser
On 12/11/13 7:16 PM, Les Mikesell wrote: I guess I don't understand why it couldn't be as simple as having the library get a pristine copy on demand if some operation needs it. The original wc code had almost no abstraction around the pristines (as far as I can recall, it's been a long time

Re: Update-Only Checkout Enhancement

2013-12-11 Thread Les Mikesell
On Wed, Dec 11, 2013 at 11:01 PM, Ryan Schmidt subversion-20...@ryandesign.com wrote: On Dec 11, 2013, at 19:19, Les Mikesell wrote: Also, it would mean you would need a constant connection to the server to use a subversion working copy. That's hardly a problem these days, You apparently