This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Details for svn test repository
Joseph S. Myers wrote:
> On Wed, 9 Feb 2005, Daniel Berlin wrote:
>
>> Again, please note that i did not convert all the tags for this test
>> repo.
>>
>> We have >1000 tags. Of those, all but about 100 are bs tags (ie merging
>> tags, unlabeled tags from rtag -F).
>> There are also 800 unlabeled branches i deleted in the latest revision
>> of the branches subdir, all from rtag -F usage.
>
> Is there a need for a flat tag/branch namespace, or could all these odd
> tags go e.g. as subdirectories of tags/unlabeled and branches/unlabeled
> when the final conversion is done?
svn itself doesn't care a whit (in fact, the namespace /tags/*,/branches/*
is actually quite optional, though cvs2svn produces it by default). The
names aren't special to svn at all, as both operations are simply copy with
history. Subfolders are fine, multiple/other dirs are are fine, whatever
suits. Most projects develop some sort of scheme though, since svn ls is
the only real facility to learn about available branches, so if it's a
total free-for-all it can be quite hard to follow.
If it's wanted, I have a little perl snippet that can do some regex-based
path rewriting on the dumpfile before you load it to move things around. I
used it to rewrite paths like /tags/Product_1_0_3 to and /trunk/Product to
a structure of /Product/trunk and /Product/tags/1.0.3, separating things
that were logically separate and just comingled in the old CVS namespace on
a previous conversion. It's a pretty simple script.
Or, one can load it as-is and just svn mv things around until the layout is
how you want it (which makes some noise in the history, but nothing
serious).
> Looking at the test repository, I see .cvsignore files as something that
> could be removed after the final move is done, being obsoleted by
> svn:ignore properties which have been initialized from the .cvsignore
> files. But I also note the following:
>
> Why is there a nonempty current svn:ignore property on gcc/doc/ when the
> .cvsignore file there was removed some time ago?
>
> How do I view the history of the changes to versioned properties on a
> directory? I can view the properties of an individual revision with svn
> proplist / svn propget, but svn log on the directory shows changes to the
> files in the directory and not changes to the properties of the directory
> itself.
property changes are included in that log (as well as changes to the files
in it). Unfortunately, though, log doesn't seem to accept -N
(non-recursive), so I guess one has to sort through the chaff.