Evaluation questions.

( SVNSCC , VS .NET, Latest, WIN 2000/XP )

Type: Public Status:Closed Created: 23 Jun 05 06:00 Updated: 23 Jun 05 06:00

--> Igor Pushkov (admin) at 23 Jun 05 06:00 writes

1. Version 1.2 of SVN now can update the files if they readonly, so one
part of our patches not needed at all. This is most critical part, since it
prevent to work combination of our plug-in with other non patched SVN
client.
Another thing that can make new SVN 1.2 is to support strict lock. Now
exist property svn::need_lock which instruct SVN make files with this
property readonly in local folder. However this option must be applied only
to selected files which really are dangerous for merging (binary files for
example). So, new SVN 1.2 mostly much better in that aspect.
But, IDE still likes when files are readonly notdepending on are they
really need lock or not. That's why we will make patched version even for
SVN 1.2.

2. Unfortunatly no. The sequence of operations not fully controlled by
plug-in. Plug-in is driven by IDE, which first want to add files, and then
commit changes.

3. Thank you we will fix this.

4. This is not true. You can send there both file revision and file url. In
terms of SVN branch or tag is just a copy of file located in some other
place. I.e. original file URL: myserver/trunk/myfile.cpp. So the branched
version will be for example at URL:
myserver/branches/release1.0/myfile.cpp.

5.1. - 5.2. I believe this is just content error, where you find that?
Currently there no way to merge branches from IDE for SVN plug-in and SVN
does not have anywhere list of tag and branches. It may be useful to look
into this discussion about this:
http://www.pushok.com/soft_svn_vscvs_1.php

And finnally, number is correct, but not always available personel who can
speak english, sorry.

--> Michael (user) at 23 Jun 05 06:00 writes

Hello!
I\'m continuing the evaluation of the SVNSCC proxy, and it looking good,
but there are still some questions and issues.

1. In the previous ticket you wrote to me that the 1.2 version somehow
solves the read only files issue and the need for your patches. Could you
please explain how? And why you still make the patches in 1.2 and why I may
want to use the patched version.

2. We notice that when commit (check in) is made from pending checkins, and
it involves modified and new (unversioned) files, it takes two revisions
(two commits) to do it - one for \'added\' and one for \'modified\'. Is it
possible to check in all them as single commit?

3. During commit the comment window pops up and when the text is inserted
it doesn\'t wrap and on enter instead of changing line it closes the
comment window and proceeds with check in.

4. This one is very importent. When \'diff\' button is pressed the very
convinient dialog is poped up. It allows to choose revision to diff with
and to brows within repository for another file. It\'s really great. What
we miss is ability to compare with file from different branch/tag, since
the brows is limited to current branch, and ability to diff with file on
disk, since the brows is limited to repository. It really not comfortable.

5. At you site it says:

5.1
>Tags & Branches.
>The plug-in package includes a program for making diffs of different
versions >and merging files. The necessity of using other SVN GUI tools is
eliminated. >All operations can be performed from IDE.

How do I start merge?? Diff with different branch??

5.2
>Visual repository and tag/branch browser.
>The plug-in contains built-in visual repository (server) browser for
viewing >available tags and branches.

How do I access thos browser??

Thank you very much,
Michael

P.S. I was trying to call you, but there are no answer. Is the number at
the site is correct one?

Rate this ticket:

Not useful at all

Partially useful

Useful

Very useful

Ticket

Evaluation questions.