On Tue, May 04, 2010 at 03:33:56PM -0400, Andy Levy wrote:
> 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."
Sounds like in John's previous job a post-commit hook was used
to update a website (served out of a working copy) whenever a commit
happened. This is described here:
http://subversion.apache.org/faq.html#website-auto-update
Stefan
Received on 2010-05-04 21:45:52 CEST