You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Mark Pearson <Ma...@uftwf.org> on 2006/06/27 16:21:47 UTC

Using svn update -rxxxx topull down new files

Hi Everyone,

 

We used to do a lot of full deployments to our production and recently
started doing more targeted deployments thus created a mixed revision
environment in Production.  We noticed that when we specified the filename
of files that existed in the working copy (Prod) the 'svn update -rxxxxx
/path/to/existing/file' worked like a charm, however, it did not pull down
new files that did not exist in the working copy.  When I specified 'svn
update -rxxxx /path/to/new/file' I get back "File not under version
control".

 

Now when I did and svn  status -verbose while in the directory where the new
files are supposed to be added I noticed that the current directory '.' was
at an earlier revision.  So I specified 'svn update -rxxxx -N .' and then
the files came down and the directory was updated as well.  In this case
this was acceptable since all the files in this directory needed to be
updated/pulled down.  But this is not what I'd like to happen.

 

Is there anyway to pull down specific 'new' files from the repository
without having to run a full 'svn update'.

 

Some background on our environment:

Our developers checkout the entire branch into the development environment
and once QA testing is complete and all the changes to files have been
committed we perform an svn update of those files into our PROD environment.
But since there is multiple projects going on in DEV we can no longer run
full 'svn updates' to PROD.  So we need to add new files to PROD.

 

Any help would be appreciated.  Thanks.

 

Mark T. Pearson
Assistant Manager of Web Administration
UFT Welfare <blocked::http://www.uft.org/>  Fund
52 Broadway, 8th Floor
New York, NY 10004
(212) 539-0605 

 


*******************************************************************************
The views, opinions, and judgments expressed in this message are solely those of the author. The message contents have not been reviewed or approved by the UFT Welfare Fund.
*******************************************************************************