You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Ich Selbst <ic...@gmx.ch> on 2002/10/07 15:21:13 UTC
behaviour request
Hi,
While trying to keep subversion synchronized with another product I stumbled
over a point about behaviour:
commands like move, delete, rename, ... expect to find the source file
intact and return with an error message if that's not the case.
This might seem correct if you use subversion ALWAYS in an own client and
don't expect it to work inside other products. For example I'm trying to
write an addin where I get several events if the user renamed, moved,
deleted a file within that IDE, but the event is just a notification that it
already
happened.
There's no way to tell the IDE that subversion would do the
rename, move, ... itself.
So my request: could subversion instead of returning with an error just do
the operation as if the file was still there and do the operation just
inside the internal structure? (only if the file is no there anymore).
So e.g. the command delete would check if the file is still there,
if yes delete it normally and from source control, if the file was
already deleted just delete the file from source control too.
kind regards,
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: behaviour request
Posted by Ich Selbst <ic...@gmx.ch>.
----- Original Message -----
From: "Karl Fogel" <kf...@newton.ch.collab.net>
To: "Ich Selbst" <ic...@gmx.ch>
Cc: <de...@subversion.tigris.org>
Sent: Monday, October 07, 2002 5:33 PM
Subject: Re: behaviour request
> "Ich Selbst" <ic...@gmx.ch> writes:
> > So e.g. the command delete would check if the file is still there,
> > if yes delete it normally and from source control, if the file was
> > already deleted just delete the file from source control too.
>
> Does the --force flag do what you need?
>
Sorry, but no.
I'm not using the command line client but an own client using the
client headers and libs. And the 'force' flags are set to true and
the functions do return with an error message 'path
f:/the_pathname_with_filename_and_extension does not exist.'
btw: my COM-wrapper is almost finished (already using it, but still got some
bugs) - any1 wants it?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: behaviour request
Posted by Karl Fogel <kf...@newton.ch.collab.net>.
"Ich Selbst" <ic...@gmx.ch> writes:
> So e.g. the command delete would check if the file is still there,
> if yes delete it normally and from source control, if the file was
> already deleted just delete the file from source control too.
Does the --force flag do what you need?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: behaviour request
Posted by Ich Selbst <ic...@gmx.ch>.
On Monday 07 October 2002 08:21, Ich Selbst wrote:
> So my request: could subversion instead of returning with an error just do
> the operation as if the file was still there and do the operation just
> inside the internal structure? (only if the file is no there anymore).
>What about URL-based deletes and moves, like
>svn rm http://server/repo/file
>svn mv http://server/repo/file http://server/repo/new-name
>and then follow those commands by an 'svn up' or something (or 'svn merge',
>since the user probably doesn't want to be forced to be at HEAD).
that's not what I want (or need) as a behaviour. URL-based deletes and moves
need network access. I want to reduce those to as less as possible (some
guys
still have dial-up).
But I think it wouldn't be much work to change the functions to behave so
that
if the 'source' file of the operation is not there anymore but present in
the .svn
directory that then the operation would execute successfully. SubVersion
would just have to ignore the errors 'file not found'...
--
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
COM binding
Posted by Ich Selbst <ic...@gmx.ch>.
Hi,
If someone's interested: attached is my version of
a COM binding for the client API.
kind regards,
Stefan
Re: behaviour request
Posted by Peter Davis <pe...@pdavis.cx>.
On Monday 07 October 2002 08:21, Ich Selbst wrote:
> So my request: could subversion instead of returning with an error just do
> the operation as if the file was still there and do the operation just
> inside the internal structure? (only if the file is no there anymore).
What about URL-based deletes and moves, like
svn rm http://server/repo/file
svn mv http://server/repo/file http://server/repo/new-name
and then follow those commands by an 'svn up' or something (or 'svn merge',
since the user probably doesn't want to be forced to be at HEAD).
I guess this isn't perfect, because a user probably will not want to have to
make a separate commit for each move. Have there been any plans for named
transactions from the command line?
svn create-txn foo
svn mv http://...
svn rm http://...
svn commit-txn foo
(also svn 'cancel-txn foo')
--
Peter Davis
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org