On 7/1/2011 1:14 PM, Andy Levy wrote:
> On Fri, Jul 1, 2011 at 13:10, Phil Pinkerton<pcpinkerton_at_gmail.com> wrote:
>> On 7/1/2011 11:38 AM, Joe.Floeder_at_sungard.com wrote:
>>> -----Original Message-----
>>> From: Andy Levy [mailto:andy.levy_at_gmail.com]
>>> Sent: Friday, July 01, 2011 10:22 AM
>>> To: Andy Levy; users_at_subversion.apache.org
>>> Subject: Re: SVN 1.7 - check out single file?
>>> On Fri, Jun 24, 2011 at 17:05, Stefan Sperling<stsp_at_elego.de> wrote:
>>>> On Fri, Jun 24, 2011 at 02:49:58PM -0400, Andy Levy wrote:
>>>>> With the new way WCs are managed, will it be possible to check out a
>>>>> single file, instead of having to do multiple steps with sparse
>>>>> directories just to get a single file in a directory? Looking at the
>>>>> release notes and CHANGES file, I think the answer is "no", but I
>>>>> someone more knowledgeable to back me up here before I take the
>>>>> back to the person who asked me. Thanks.
>>>> No, you still need to checkout a directory. But it sounds like the
>>>> new --parents option of svn update might help you a bit:
>>> We'll have to see how Tortoise implements this, as that's what most
>>> folks here are using.
>>> It's an edge case for us, it's only 2 or 3 people who are affected by
>>> the issue of too many items to check out just to update a single file.
>>> There may be more people who would like this feature than you think.
>>> Actually this ability is just what we are looking for. We are migrating
>>> off of SCCS and RCS to SVN. We organize our 9000 source files into two
>>> directories. We were disappointed that svn did not allow single file
>>> checkout. 90% of our work is maintenance involving 'work tickets' that
>>> affect only one or two files. So right now, in test, our checkouts run
>>> 4-10 minutes (depending on other server tasks and network traffic).
>>> This, as an optional ability, would be great for us.
>> On the same note I have been involved with migrating some 200 VSS databases
>> to Subversion, one of the big issues is the ability to checkout a single
>> file, we default to using export in those cases as many checkouts , updates
>> and commits are done via scripts.
>> The other issue with regards to functionality of Subversion vs VSS is that
>> many times VSS gets files from multiple locations in the database and puts
>> them in the working directory. We find it difficult if not impossible to do
>> the same with Subversion.
> In what ways could svn:externals be improved to do what you need?
> My memories of "sharing" in VSS are all nightmares.
No doubt about VSS that is why I convinced the entire Enterprise that it
was not the appropriate application for source code management and
Just having the ability to checkout a single file via TortoiseSVN or the
commandline would be a huge gain for us.
I am trying to promote changing the development process but too many
legacy applications still exist that have dependencies on VSS where
developers are not able or even willing to change to optimize the
utilization of Subversion. We have a hack in place to handle the worst
offending application that was built around VSS.
Received on 2011-07-01 19:26:51 CEST