Aaron Hilton wrote:
> Hi Daniel,
>
> I don't mean to sound too harsh, it's just a pet peeve, and I really
> like what SVN can already do.
>
> Anyway, loading a file by using "svn import" with a --replace variant
> would have its benefits too.
> But, I just want to say:
> svn commit -m "I don't care there was a change, just use this one
> instead." --force thisfile.bin
>
> In your oppinion, is this difficult to implement?
Ah, I think I understand what you're looking for, and it's a little
different to what I was thinking of.
You'd like something like:
svn update --dont-conflict-and-keep-my-changes (there's got to be
a better string than that)
or
svn commit --ignore-out-of-dateness
I have to say, while I can kind of understand where you're coming from
on that, I don't think it's such a great idea. In a busy environment,
you probably wouldn't want an option like that available. There has
been a lot of work put into Subversion to ensure that you can't
unknowingly discard someones changes.
If you implement a feature like this, then you might not replace the
file you think you're replacing. If someone slips in a commit
between when you looked at the repository, and when you commit,
you'd replace their changes and not even realise. That's what the
up-to-dateness check before a commit is all about. However, I'm
sure you realise that :-)
I think that the features I outlined above wouldn't be that hard
to implement (they're basically just optionally turning off some of
the consistency checking that's done right now). I don't think
it's a good idea personally.
As to whether it'd get into the codebase if a patch was submitted,
well, you'll have to ask on the dev@ list :-)
daniel
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Mar 13 11:02:06 2005