If you want to follow SVN commits on some of my SVN repositories, you can subscribe to appropriate maling list, which gets notification on each SVN commit. I hope I set up mailman correctly and everything will work as I expect :-).
This list is also automatically forwared to packages.qa.debian.org, so you can also subscribe there for Debian package changes.
If you want to follow SVN commits on some of my SVN repositories, you can subscribe to appropriate maling list, which gets notification on each SVN commit. I hope I set up mailman correctly and everything will work as I expect :-).
This list is also automatically forwared to packages.qa.debian.org, so you can also subscribe there for Debian package changes.
If you want to follow SVN commits on some of my SVN repositories, you can subscribe to appropriate maling list, which gets notification on each SVN commit. I hope I set up mailman correctly and everything will work as I expect :-).
This list is also automatically forwared to packages.qa.debian.org, so you can also subscribe there for Debian package changes.
If you want to follow SVN commits on some of my SVN repositories, you can subscribe to appropriate maling list, which gets notification on each SVN commit. I hope I set up mailman correctly and everything will work as I expect :-).
This list is also automatically forwared to packages.qa.debian.org, so you can also subscribe there for Debian package changes.
After more playing with Tailor, I managed to hack it enough to convert my Arch repositories to Subversion. Move from distributed to non distributed VCS migth look as step backwards, but I have pretty good reasons for this:
The conversion is currently on the way and will probably need some time (about half of Gammu revisions have been converted so far).
After more playing with Tailor, I managed to hack it enough to convert my Arch repositories to Subversion. Move from distributed to non distributed VCS migth look as step backwards, but I have pretty good reasons for this:
The conversion is currently on the way and will probably need some time (about half of Gammu revisions have been converted so far).
After more playing with Tailor, I managed to hack it enough to convert my Arch repositories to Subversion. Move from distributed to non distributed VCS migth look as step backwards, but I have pretty good reasons for this:
The conversion is currently on the way and will probably need some time (about half of Gammu revisions have been converted so far).
After more playing with Tailor, I managed to hack it enough to convert my Arch repositories to Subversion. Move from distributed to non distributed VCS migth look as step backwards, but I have pretty good reasons for this:
The conversion is currently on the way and will probably need some time (about half of Gammu revisions have been converted so far).
After more playing with Tailor, I managed to hack it enough to convert my Arch repositories to Subversion. Move from distributed to non distributed VCS migth look as step backwards, but I have pretty good reasons for this:
The conversion is currently on the way and will probably need some time (about half of Gammu revisions have been converted so far).