On Wed, Jul 22, 2009 at 3:15 PM, Ryan Schmidt <
subversion-2009b_at_ryandesign.com> wrote:
> On Jul 22, 2009, at 15:10, Robert Dailey wrote:
>
>> On Wed, Jul 22, 2009 at 2:32 PM, Erik Huelsmann wrote:
>>
>>> On Wed, Jul 22, 2009 at 9:18 PM, Robert Dailey wrote:
>>> > What limitations are placed on the repository while the commit is in
>>> > progress?
>>>
>>> None. There is a limitation placed on the commit though: if any item
>>> the commit changes is also changed in the mean time, the commit may be
>>> rejected with an "out-of-date" error.
>>>
>>
>>
>> If this is true, this seems problematic. What if the team is making a
>> commit every 5 minutes? Assuming each commit the team makes touches at least
>> one of the files you are committing, then you will never be able to
>> successfully commit your changes. Ever.
>>
>
> It sounded like a pretty hypothetical problem to me. What kind of commit
> would ever take 24 hours, or even 1 hour? Unless you're committing large
> binary files over a slow network, but binaries aren't mergeable so people
> shouldn't be simultaneously modifying those anyway.
>
>
You're right, I wasn't being practical. But since when did unit tests have
to be practical? :)
Thanks for the information guys. Good stuff.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2374562
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-07-22 22:18:45 CEST