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

Re: Regarding shallow checkouts

From: An Me <annminz_at_gmail.com>
Date: Tue, 23 Feb 2010 10:18:50 +0530


Thanks for the reply.

But usually if we are working on java project,to edit some files mean we
need to co the whole project and not that single file alone for editing as
we need to check whether the whole project is working fine by finally
compiling and running the same.So where exactly is the shallow co useful?


On Mon, Feb 22, 2010 at 9:54 PM, Andrey Repin <anrdaemon_at_freemail.ru> wrote:

> Greetings, An Me!
> > I am learning svn and am a new-bie.The following is my doubt.
> > What is the significance of shallow checkouts.?.
> > Why would somebody want to checkout a project partially.?
> > If possible please explain with a scenario/real life example.
> If by shallow checkout you mean fetching of only certain depth of subdirs,
> then "real-world" example is quite simple.
> You need to change only one file. You co empty top-level directory, then
> update only that file. And edit and commit it.
> --
> WBR,
> Andrey Repin (anrdaemon_at_freemail.ru) 22.02.2010, <19:22>
> Sorry for my terrible english...
Received on 2010-02-23 05:49:27 CET

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.