[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Checkins without prior checkout avoiding WC?

From: Peter Valdemar Mørch <swp5jhu02_at_sneakemail.com>
Date: 2004-08-20 15:06:03 CEST

Max, thank you for your reply.

 From your reply I take it that my assumption is correct: checkin
without a working copy is not currently possible.

Max Bowsher maxb-at-ukf.net |Lists| wrote:
> You should take a look at the svn_ra API. Whilst it is very WC oriented,
> at no point does it assume anything about the format - so your WC could
> be a set of data structures in memory - or shipped to and from the
> client in a cookie.

I will, thank you. I don't mind submitting patches to the svn client
that are accepted and made generally available, if there is no objection
  in principle to doing what I intend - ci without a working copy.

But I don't want to have to ship a custom "hacked" svn client binary (or
*any* binary) with this PHP app. It has to work with a (potential future
version of) the vanilla svn client. Is this a feature that could be
allowed in to the standard svn client with a published command-line api?
If not, I'll just stick to using a working copy, even tough it is
pointless from the perspective of this particular application.

> We are talking about a web form here? Then why not just...

Yes there are countless ways I can detect conflicts outside of svn.
Implementation details. (I'm thinking of a WebSVN level "locking"
mechanism, that eventually will be mapped into the "real" >1.2 svn
exclusive locking mechanism, but your method would work too)



Peter Valdemar Mørch
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Aug 20 15:06:27 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.