You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by "T. Wassermann" <ma...@tobias-wassermann.de> on 2006/06/30 05:15:46 UTC
(Feature request?) svn delete only in repository
Hi Guys,
we have the following situation:
In a repository somebody checked in the file config.inc.php. This file
contains some configuration settings that are different for every local
machine.
Now it wouldn't be efficient if anybody can commit the own version of
this file. We have to remove it from the repository with svn delete,
but: We don't want to delete it from the wc's when the users calls svn
update.
It would be nice if we can:
- call svn delete with an switch like --no-wc-remove
- the file will be deleted from repository, the *physical file* in the
working copies will not be removed - the file is no longer under version
control, right - but the file exists, the users have not to recreate it.
After this operation somebody can add this file to svn:ignore.
So this problem a colleague have had too - I think it happens sometimes,
you're adding file to version control and later you mention that's bad
if this files are under version control, but you'll not remove this file
from the existing working copy directories...
Best Regards
Tobias
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Re: (Feature request?) svn delete only in repository
Posted by Peter Werner <l....@vasas.no-ip.org>.
If that config.inc.php is really different for developers then it can
simply be removed from the repository and added to svn:ignore. svn
update will not remove it from the local copy if it has local
modifications.
WP
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: Re: (Feature request?) svn delete only in repository
Posted by "Daniell, Casey B" <Ca...@reyrey.com>.
It sounds like the OP knows that this isn't a current feature, hence the
Feature Request. What he is noting is:
1. A places a file into version control.
2. The file is not a good candidate for being version controlled (in
this case because everyone has a different copy of it)
3. He would like to have SVN silently remove the file from version
control, but preserve the copy that everyone has in their WCs.
Yes, the template is the correct thing to do, if it was thought about
before hand, however, this is a case where users are trying to overcome
a mistake that a developer made. This mistake, in large teams is can be
very costly to over come especially, if you have to tell everyone and
have the do the manual copy file to temp loc, update, copy it back.
Especially since we all know that devs will read and follow all their
email before doing the next update....
This is a convenience request for making SVN more scalable, and offering
recovery solutions when folks put something into VC that shouldn't be
there.
Casey
-----Original Message-----
From: Ryan Schmidt [mailto:subversion-2006q2@ryandesign.com]
Sent: Friday, June 30, 2006 5:39 AM
To: T. Wassermann
Cc: users@subversion.tigris.org
Subject: Re: (Feature request?) svn delete only in repository
On Jun 30, 2006, at 07:15, T. Wassermann wrote:
> In a repository somebody checked in the file config.inc.php. This file
> contains some configuration settings that are different for every
> local machine.
>
> Now it wouldn't be efficient if anybody can commit the own version of
> this file. We have to remove it from the repository with svn delete,
> but: We don't want to delete it from the wc's when the users calls svn
> update.
>
> It would be nice if we can:
>
> - call svn delete with an switch like --no-wc-remove
>
> - the file will be deleted from repository, the *physical file* in the
> working copies will not be removed - the file is no longer under
> version control, right - but the file exists, the users have not to
> recreate it. After this operation somebody can add this file to
> svn:ignore.
>
> So this problem a colleague have had too - I think it happens
> sometimes, you're adding file to version control and later you mention
> that's bad if this files are under version control, but you'll not
> remove this file from the existing working copy directories...
Subversion doesn't offer that. This is a suggested way to handle this
situation:
http://subversion.tigris.org/faq.html#ignore-commit
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: (Feature request?) svn delete only in repository
Posted by Ryan Schmidt <su...@ryandesign.com>.
On Jun 30, 2006, at 07:15, T. Wassermann wrote:
> In a repository somebody checked in the file config.inc.php. This
> file contains some configuration settings that are different for
> every local machine.
>
> Now it wouldn't be efficient if anybody can commit the own version
> of this file. We have to remove it from the repository with svn
> delete, but: We don't want to delete it from the wc's when the
> users calls svn update.
>
> It would be nice if we can:
>
> - call svn delete with an switch like --no-wc-remove
>
> - the file will be deleted from repository, the *physical file* in
> the working copies will not be removed - the file is no longer
> under version control, right - but the file exists, the users have
> not to recreate it. After this operation somebody can add this file
> to svn:ignore.
>
> So this problem a colleague have had too - I think it happens
> sometimes, you're adding file to version control and later you
> mention that's bad if this files are under version control, but
> you'll not remove this file from the existing working copy
> directories...
Subversion doesn't offer that. This is a suggested way to handle this
situation:
http://subversion.tigris.org/faq.html#ignore-commit
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: (Feature request?) svn delete only in repository
Posted by "T. Wassermann" <ma...@tobias-wassermann.de>.
>
> copy config.inc.php %TEMP%\config.inc.php
> svn update
> move %TEMP%\config.inc.php config.inc.php
>
Hi,
this solution is good, when only one user has to do this. But if you're
having many users it's not practicable. We think the best solution
should not require any additional action by the working-copy-users (they
should *only* call svn update).
Regards
Tobias
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: (Feature request?) svn delete only in repository
Posted by Steve Williams <st...@kromestudios.com>.
T. Wassermann wrote:
> Now it wouldn't be efficient if anybody can commit the own version of
> this file. We have to remove it from the repository with svn delete,
> but: We don't want to delete it from the wc's when the users calls svn
> update.
>
> It would be nice if we can:
>
> - call svn delete with an switch like --no-wc-remove
>
> - the file will be deleted from repository, the *physical file* in the
> working copies will not be removed - the file is no longer under version
> control, right - but the file exists, the users have not to recreate it.
> After this operation somebody can add this file to svn:ignore.
>
copy config.inc.php %TEMP%\config.inc.php
svn update
move %TEMP%\config.inc.php config.inc.php
--
Sly
This message and its attachments may contain legally privileged or confidential information. This message is intended for the use of the individual or entity to which it is addressed. If you are not the addressee indicated in this message, or the employee or agent responsible for delivering the message to the intended recipient, you may not copy or deliver this message or its attachments to anyone. Rather, you should permanently delete this message and its attachments and kindly notify the sender by reply e-mail. Any content of this message and its attachments, which does not relate to the official business of the sending company must be taken not to have been sent or endorsed by the sending company or any of its related entities. No warranty is made that the e-mail or attachment(s) are free from computer virus or other defect.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org