Repository/development issues

[Malte S. Stretz]

Hi folks,

I had a look at the m0n0 source to see how hard it could be to add some
things I need. As described in [1] I tried to find the most recent
version in trunk but that one only contained stale code from a few years
ago.

It didn't take me too long to find out that the 1.3 development is
happening in /branches/freebsd6. It was still a bit confusing, so I
think either it is time for an
svn mv /branches/freebsd6 /trunk
or [1] should be updated and maybe the trunk rm'd.

While looking for the most recent codebase, I also noticed that for the
last few releases no tags were created. Which should be quite easy to
fix, attached you can find the file revs.txt and if somebody with the
proper permissions executes the following bash snippet, everything
should be fine ("should" I said, remove the safety-colon in front of the
svn command):

while IFS=: read _ v _ _ _ b r; do
R=http://svn.m0n0.ch/wall
: svn cp $R/branches/$b@$r $R/tags/release-$v
done < revs.txt

I created the file by downloading the embedded images and extracting the
build times with a script and comparing the times to the output of svn
log. I attached the script too, not because it is terribly useful but
because it is an easy way to archive it :) I'm running Linux and it
took me a while to find out how to access the rootfs, finding the
correct offsets and mount parameters and stuff.

Cheers,
Malte

[1]http://m0n0.ch/wall/repository.php

--

[Manuel Kasper]

Hello,

Post by Malte S. Stretz
It didn't take me too long to find out that the 1.3 development is
happening in /branches/freebsd6. It was still a bit confusing, so I
think either it is time for an
svn mv /branches/freebsd6 /trunk
or [1] should be updated and maybe the trunk rm'd.

Good idea - done (-> trunk removed to avoid further confusion :).

Post by Malte S. Stretz
While looking for the most recent codebase, I also noticed that for the
last few releases no tags were created. Which should be quite easy to
fix, attached you can find the file revs.txt and if somebody with the
proper permissions executes the following bash snippet, everything
should be fine ("should" I said, remove the safety-colon in front of the

Cool! I've just run your shell script, so the missing tags are now in place. Thanks!

Cheers,

Manuel