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

Re: Committing changes

From: Andy Levy <andy.levy_at_gmail.com>
Date: Tue, 4 May 2010 15:33:56 -0400

On Tue, May 4, 2010 at 15:17, John Doe <warlockleviathan_at_gmail.com> wrote:
> Hi
>
> Hope this is the right place to ask about this. My question is best
> asked with a scenario of the situation:
>
> Your web server root is at C:\webs
> You set up C:\SVN as the repository
> Now, you add c:\webs\test to the repository
> You check out a copy of the 'test' directory to work on
> You make some mods and then commit the changes
> In the repository browser, if you open a file it reflects the changes
> you made in the working copy and commited.
> Should the mods be reflected in c:\webs\test? Since that is the
> initial directory added so I was under the impression that a commit
> would update these files. If I am under the wrong impression then my
> understanding of SVN from my previous job is wrong.

c:\webs\test has no connection to the repository at all, so it cannot
be updated from the repository. If you do an "in-place import" from
c:\webs\test, it will be a working copy, so you can run svn update to
pull the updates down to it. See
http://subversion.apache.org/faq.html#in-place-import for information
on performing an in-place import.

Any working copies you have must have svn update explicitly executed
against them for the updates to be retrieved. Subversion is a "pull"
system, not "push."
Received on 2010-05-04 21:34:45 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.