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

SVN status code and server/client responses - quick questions

From: Z W <mpc8250_at_gmail.com>
Date: Tue, 26 Mar 2013 01:24:50 -0700

Hi All

We're new to SVN.
We think we got the basics but like to know more.

We having been using SVN updates with Hudson and it uses the SVNkit as
a SVN client.
We notice that sometimes zip file is NOT updated from the SVN server.

On another occasion, we're not sure why when someone checks in their
jars, the SVN client sees that as a conflict.
We could see that the SVN status code is not a U but a C or a M.

We like to know
1) why is the zip file not updatable by the client
2) How does the server or the client determine the SVN status code and
then determine its action whether to update or requires manual
conflict resolution.
3) When the client shows an M or something else other than U, A or
AU, do we have to worry about any conflicts not resolved. At this
point, we know C is bad news.
4) How does AU differ from A; we see this when we do a fresh checkout.

Thanks All
Sincerely
Received on 2013-03-26 09:25:27 CET

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.