Thanks All for your help and advices,
>> From: Les Mikesell :
> svn logs will show file/directory additions/deletions in the parent
directory, so you should be able to track the history of things that way if
you wanted, but what is it that you specifically need to do?
> Most people would just check out some directory level and diff it against
some other revision or a branch or tag.
Ok, svn log -v will help,
But :
With CC, I can easily search for any file element in a repository, and
directly get its path,
With SVN, I have to check all revisions, then I can know where this element
is located in the repository (maybe several locations), I can find in which
revision it was removed.
This is double manual search.
When users ask for help, I have to go in their repository that I don't know
at all, users often give less than half the information I need to locate
the file where they need help.
With CC, I can quickly analyze a repository, and get easily the missing
information.
With SVN, I feel like blind, because I cannot do the same analysis on the
repository. I cannot do a global search, I have to check the revisions
individually.
About peg revision :
Peg revision means that I can access any file and directory "version"
without checkout, this is already a nice help.
But : is there also an individual identifier for directory and file (uuid,
oid, ..) ?
>> From: Andrew Reedick
> I used to use ClearCase in a past life (3.0 - 6.0). I haven't missed the
ability to diff dirs. You might be stuck on doing things the CC way
instead of learning the Subversion paradigms. It's going to be frustrating
for a little while (it was for me.)
> What are you trying to do that requires diff'ing the contents of
directories?
Could you help more on diff dirs, please :
- What is the best way with SVN to compare a same directory on two
different branches ?
I am very confused by many things with SVN, one of them is :
- I can merge from any directory to any directory anywhere, and I just get
a terrible Tree conflict.
With CC, the merge is inside the version tree of the file or directory
element. This kind of mistake is not possible.
I don't understand why it is done like this with SVN.
I did not understand everything with branches and tags, I have to read
again the manual, but I have the feeling that branches and tags are not
linked, this is strange to me.
>> From: Andrew Reedick
> To re-emphasize, I'm very serious about the need to stop trying to apply
CC paradigms to SVN. It's frustrating, and, in my experience, the CC way
of doing things didn't provide significant advantages in (or over) SVN.
I understand, and I don't try to use SVN "in the CC way". SVN and CC are
tools, the goal for me is the software configuration management of the
projects,
and also to be able to help the users of the tools in the best way.
On the other hand, I'd like to understand and compare the capabilities of
both tools by myself, because what I read in the past was not detailed
enough in my opinion.
Thanks
2013/6/11 Olivier Antoine <oliviera201304_at_gmail.com>
> Hi,
>
> I'm trying to work with SVN, but coming from ClearCase, I'm lost.
>
> It seems that it is not possible to consult the history of the repository
> like in CC,
> I can get the history of a file element with svn+annotate, I can use
> svn+diff on files,
> But for directories : no annotate, no diff - nothing ?
> Do I have to check all the repository revision set in order to follow the
> changes on a directory element ?
>
> Regards
> Olivier
>
>
Received on 2013-06-12 21:42:13 CEST