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

Re: some subversion issues

From: Ulrich Eckhardt <eckhardt_at_satorlaser.com>
Date: Tue, 27 May 2008 11:39:48 +0200

On Tuesday 27 May 2008, maheshwar singh wrote:
> Q1:
> Does Subversion allow non-linear editing of versionscreate v1 -> put in VMS
> v1edit v1 to make v2 -> put in VMS v2edit v2 to make v3 -> put in VMS
> v3realise v3 is a mistake; get v2 from VMS to editso now system looks like:
> Local version v2 ; VMS version v3edit v2 to make v4 (or a new v3 depending
> on semantics) -> put in VMS**after adding to subversion I cannot see this
> version that I have added - where is it? I cannot get itif i look at
> history i see the 3 original versions - there is NO version 4 & the version
> 3 is the original version 3;if i say Get Latest Version or get v3 I get the
> original v3

I'm not clear what you mean here. If you actually check in three files foo1,
foo2 and foo3, they are treated as different files by SVN, even if they
represent different versions of the same file. In order to get SVN to version
them, you need to use the same name.

> Q2.
> How can i lock a file or make other users aware that the file has been
> checked out by User A.I know subversion does not allow locking, i'm looking
> for any mechanism available that will warn User 1 that User 2 has checked
> out the file, User 1 can then call User 2 about the changes.

You can't. Any use could check out as many working copies as they want. They
could even copy the working copy locally without the repository (as central
point for all users) even knowing. Or they could delete them, without the
repository knowing either. Why would you need that?

> Q3.
> I delete a file from the local system due to a mistake, is there any way i
> can get a list of objects that exist in the subversion repository and not
> in the local system.

See the 'ls' and 'status' commands.

> Q4.When 2 users are have requested for latest version of same document and
> working on 2 different changesExample in a Sales Revenue reportUser 1 - Add
> Margin to the reportUser 2 - Add Discount to the reportBoth change are
> check in at the same time by the respective users.

Two users can't check in at the same time. Checkins are atomic and they are
serialised, i.e. one will be the first, the other will be the second to check

> Only one user change is reflected and the other user change is lost.

No, one will commit their changes and the others will be told to first update
their working copy. Note that in the case of most binary formats SVN won't be
able to merge in the changes during an update, so it requires manual
interaction to merge. I suggest using locking on non-mergable files.

BTW: the formatting of your mail is pretty messed up. My guess is that it
still looks okay in the HTML part (which, according to the guidelines you
shouldn't have used in the first place) but is broken in the text part.



ML: http://subversion.tigris.org/mailing-list-guidelines.html
FAQ: http://subversion.tigris.org/faq.html
Docs: http://svnbook.red-bean.com/
Sator Laser GmbH
Geschäftsführer: Thorsten Föcking, Amtsgericht Hamburg HR B62 932
           Visit our website at <http://www.satorlaser.de/>
Diese E-Mail einschließlich sämtlicher Anhänge ist nur für den Adressaten bestimmt und kann vertrauliche Informationen enthalten. Bitte benachrichtigen Sie den Absender umgehend, falls Sie nicht der beabsichtigte Empfänger sein sollten. Die E-Mail ist in diesem Fall zu löschen und darf weder gelesen, weitergeleitet, veröffentlicht oder anderweitig benutzt werden.
E-Mails können durch Dritte gelesen werden und Viren sowie nichtautorisierte Änderungen enthalten. Sator Laser GmbH ist für diese Folgen nicht verantwortlich.
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-05-27 11:44:46 CEST

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.