Hi All,
Thank you all for the response.
Regards,
An
On Tue, Feb 23, 2010 at 11:23 AM, Ryan Schmidt <
subversion-20...@ryandesign.com> wrote:
>
> On Feb 22, 2010, at 22:48, An Me wrote:
>
> > On Mon, Feb 22, 2010 at 9:54 PM, Andrey Repin wrote:
> >
> >> You need to change only one file. You co em
On Feb 22, 2010, at 22:48, An Me wrote:
> On Mon, Feb 22, 2010 at 9:54 PM, Andrey Repin wrote:
>
>> You need to change only one file. You co empty top-level directory, then
>> update only that file. And edit and commit it.
>
> But usually if we are working on java project,to edit some files mea
Hi
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
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 fetchin
Well, my scenario is simple: I have a repository that contains a folder
branches and in that folder is a branch for every version that is deployed.
Deployment is done every second week, since 2007. So that's a lot of branches.
I use shallow checkout to check out the branches folder and all of it
Hi All,
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.
Regards,
An
