Mark Phippard wrote:
> This command:
>
> svn ci --force -m "Commit out of date file" FOO
>
> Does not allow you to commit an out of date file. So JavaHL would not
> allow it either. In fact, the above command yields this error:
>
So it does. Why is that? Shouldn't I be able to force a commit? I can
with CVS.
The situation is:
1) I have a file which is out-of-date by virtue that someone else has
committed a new version and I haven't yet updated. Let's say that the
base revision of my file is 100 and revision 105 is the latest in the
repository.
2) My own copy of the file has local changes
3) I want to commit my copy as the new version, without
incorporating/merging any changes
Surely there is there some way to do this (from the command line)?
(Ideally, it would involve specifying that I specifically want to
replace revision 105, so that if there have been subsequent commits that
I'm not aware of I will still get a conflict; that is, the commit would
not be totally unconditional).
I guess I can check out the file to a temporary directory, copy my
changed version over it and then commit it from there. But I thought
that there'd be a better way.
> but JavaHL only exposes libsvn_client by
> design. That is what makes it a "high level" API.
Sure, but what I am talking about really is a "high level" operation.
> If the low level
> Subversion API can do this, then you can probably do it using SVNKit.
>
> http://svnkit.com/
>
I was hoping to avoid using SVNKit-specific functionality. It would be
nice if what I am doing would work with either JavaHL + native bindings
or SVNKit.
Thanks for your response,
Davin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-03-07 02:46:54 CET