I'm not seeing a mail list at svnkit.com yet. I hope the author (Alex
isn't it?) still lurks here.
1. Can you make the default behaviour in svnkit to /not/ upgrade a
working copy? It's extremely frustrating to have a subversion client
change a WC so that other clients on the same machine can no longer use it.
2. If svnkit moves (delete+add) a file into a new directory, the
metadata is updated from 1.3 to 1.4 anyway, regardless of the upgradeWC
setting. Again this means I can no longer use my command line client.
Please don't take this as a moan - I'm a huge fan of both subclipse and
the javasvn adapter.
Mark Phippard wrote:
> On 12/6/06, *Dan North* <firstname.lastname@example.org <mailto:email@example.com>>
> Hi Mark.
> I know you're not the right person to ask, but you always know
> anyway, so...
> What's the magic system property to stop the new svnkit upgrading my
> working copy?
> ps. It upgraded the wc anyway today out of spite, but we're
> talking again.
> It is the same values you indicated in this email:
> You can see it in the SVNKit source here:
> Mark Phippard wrote:
> > I will probably do a 1.1.9 release late today or tomorrow. Most
> > likely tomorrow. There is nothing overly significant (that I can
> > remember) coming in this release, but there are several small fixes
> > and enhancement. The main thing is to get the latest JavaHL and
> > SVNKit versions out there. It also contains some stuff we need out
> > there for the Mylar 1.0 release which is coming soon as well as an
> > improvement in our headless support that Buckminster needs.
> > Just a heads up.
> > Mark
> To unsubscribe, e-mail: firstname.lastname@example.org
> For additional commands, e-mail: email@example.com
Received on Wed Dec 6 22:49:12 2006