On Thu, Jul 16, 2009 at 10:56:28AM -0400, Christopher Clarke wrote:
> On 07/16/2009 10:51 AM, Mark Phippard wrote:
> > On Thu, Jul 16, 2009 at 10:48 AM, Christopher
> > Clarke<tigris.org_at_fuscata.com> wrote:
> >> What do you think about making the --keep-local flag work for everyone's
> >> working copy?
> >>
> >> For example, I want remove myfile.txt from the repository but not delete
> >> it locally, so I: svn delete --keep-local myfile.txt
> >>
> >> Why should this delete the file locally from anyone else's working copy?
> >> Why not just leave it in all working copies too?
> >
> > There is no way to do this without making some kind of major change to
> > have this new information stored in the repository. Meaning there
> > would have to be a way to know the difference between a delete and a
> > delete with keep local.
> >
>
> What about adding it as a property?
You keep asking us to fix this problem from within Subversion,
but have not yet responded to my questions and suggestions about how
your own process could be tweaked in order to avoid this problem.
I think that fixing your process will get much quicker results,
since a fix made within Subversion will take quite a long time to make,
and then also needs to propagate to all the various Subversion clients
your peers are using.
And fixing the problem within Subversion will require developer resources
which are fairly scarce. And quite frankly, "[My] peers have different
levels of technical ability and [...] I can't expect them all to do this
properly" and "It's a 1 time pain for everyone on the team every time I
need to do this. That costs [us] $$$." are not exactly reasons which will
cause a developer to quickly jump and spend time on it while there are
much more interesting and important problems to solve for our users.
Stefan
Received on 2009-07-16 19:28:02 CEST