You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Bryan Andrews <ba...@trendinfluence.com> on 2004/03/31 17:25:27 UTC
Issue with updating when folder already exists on local hard drive
This issue seems to come up often:
We have a local folder that is part of a project but is not in source control for example lets call it "externalimages". Several developers may have this folder. A decision is made that this folder should be added to source control, it is added by one developer, now the next developer who tries to update will have a problem if they too had this folder in their project (the SVN client does not want to overwrite it).
Is there a way to prompt to overwrite this local folder/contents from the subversion repository rather than fail on the update?
Thanks.
Re: Issue with updating when folder already exists on local hard
drive
Posted by Ben Collins-Sussman <su...@collab.net>.
On Wed, 2004-03-31 at 11:25, Bryan Andrews wrote:
> Several developers may have this folder. A decision is made that this
> folder should be added to source control
This situation happens *often*? I agree with Jan's response about
needing more communication in your team. It sounds like the more
fundamental problem here is coming to an agreement about what should be
under version control in the first place. This shouldn't be a common
scenario.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Issue with updating when folder already exists on local hard drive
Posted by Jan Hendrik <ja...@bigfoot.com>.
Concerning Issue with updating when folder alr
Bryan Andrews wrote on 31 Mar 2004, 12:25, at least in part:
> This issue seems to come up often:
>
> We have a local folder that is part of a project but is not in source
> control for example lets call it "externalimages". Several developers
> may have this folder. A decision is made that this folder should be
> added to source control, it is added by one developer, now the next
> developer who tries to update will have a problem if they too had this
> folder in their project (the SVN client does not want to overwrite
> it).
>
> Is there a way to prompt to overwrite this local folder/contents from
> the subversion repository rather than fail on the update?
Some good communications in the team is necessary:
While one developer adds and commits this folder, the other have
to move their copies of the folder out of the way. After updating
their working copies they have this folder under version control, too.
Now this versioned folder must be synchronized with their original
one (except for the .svn folder area) and committed.
Jan hendrik
---------------------------------------
Freedom quote:
A wise and frugal government, which shall restrain men from
injuring one another, which shall leave them otherwise free to
regulate their own pursuits of industry and improvement, and shall
not take from the mouth of labor the bread it has earned. This is
the sum of good government, and all that is necessary to close the
circle of our felicities.
-- Thomas Jefferson, in his 1801 inaugural address
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org