ATT: svn.kde.org has been updated

[Adriaan de Groot]

On Sunday 10 April 2005 15:09, Stephan Kulow wrote:
> You can browse it as long as websvn is offline at
> https://svn.kde.org/viewcvs
>
> Notice (and give feedback) on the structure of /branches and /trunk.

Perhaps you should end each message about SVN with a link to a previous 
message or webpage or tutorial or primer or whatever to avoid the legion of 
d00fuses that will ask "pardon me, but what was the intended scheme again?"

I see a branches/cvs/lambda_reduce_1 which should be in kdepim/work (or 
work/kdepim? or work/lambda_reduce_1? Referring to your -core-devel message 
from 2005-03-31 15:36, subject "SVN timing", I guess that latter). Sorry 
about not noticing it earlier: I was looking for _other_ people's branches 
you'd forgotten last time you asked, not my own.

So are the contents of /branches/ basically random? I see some release 
branches sorted by app, some old branches sorted by CVS module, and lots of 
"other".

Similarly, will /tags/ be sorted in the same way as /branches/ ? Or is some 
other scheme going to be applied there? Right now there is no structure at 
all, and while I can sort out the ARTS_x_y_RELEASE tags easy enough, some 
weird-ass tag like before_merging_head_to_kpilot _probably_ belongs under the 
kpilot tags (or the PIM tags) ... that is, assuming there is to be structure 
in /tags/.

Finally, /trunk/ has several differnet bits for websites -- developer.kde.org, 
events.kde.org and www/ . Is that to be sorted out _after_ the conversion to 
SVN? I believe you said so on -www, but memory fails.

Finally++, kckde/, as a defunct bit of interesting KDE history -- right there 
in trunk/ ? I suppose that depends on whether you want to have the SVN 
hierarchy intuitively obvious and uncluttered, but deep (which sort of 
precludes obviousness) or not.

-- 
These are your friends - Adem
    GPG: FEA2 A3FE Adriaan de Groot