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

RE: SVN 1.7 - check out single file?

From: <Joe.Floeder_at_sungard.com>
Date: Fri, 1 Jul 2011 11:38:48 -0400

-----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
need
>> someone more knowledgeable to back me up here before I take the
answer
>> 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:
>
http://subversion.apache.org/docs/release-notes/1.7.html#update-parents

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.
Received on 2011-07-01 17:40:40 CEST

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

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