Tags

Tags give the ability to mark specific points in history as being important

KDE 3.90.1 (KDE 4.0 alpha1) - Try #1

svn path=/tags/KDE/3.90.1/kdeutils/kdf/; revision=660709

3.80.3

svn path=/tags/KDE/3.80.3/kdeutils/kdf/; revision=635538

create KDE 3.5.6

svn path=/tags/KDE/3.5.6/kdeutils/kdf/; revision=623901

redo it consistently

svn path=/tags/KDE/3.5.5/kdeutils/kdf/; revision=591452

tagging KDE 3.5.4

svn path=/tags/KDE/3.5.4/kdeutils/kdf/; revision=565692

tagging - first step

svn path=/tags/KDE/3.5.3/kdeutils/kdf/; revision=544025

tagging second time

svn path=/tags/KDE/3.5.2/kdeutils/kdf/; revision=519807

finally tagging 3.5.1

svn path=/tags/KDE/3.5.1/kdeutils/kdf/; revision=500400

tagging KDE 3.5.0 - will have to retag later

svn path=/tags/KDE/3.5.0/kdeutils/kdf/; revision=479118

finally tagging 3.5 beta2

svn path=/tags/KDE/3.4.92/kdeutils/kdf/; revision=469461

tagging 3.4.3

svn path=/tags/KDE/3.4.3/kdeutils/kdf/; revision=467549

another sync of tag and tar ball

svn path=/tags/KDE/3.4.91/kdeutils/kdf/; revision=462492

Dirk is stressed with the difference between tag and tar ball - and 
I don't care too much

svn path=/tags/KDE/3.4.90/kdeutils/kdf/; revision=462490

creating 3.4.2 tag

svn path=/tags/KDE/3.4.2/kdeutils/kdf/; revision=436917

tagging KDE 3.4.1 and arts 1.4.1

svn path=/tags/KDE/3.4.1/kdeutils/kdf/; revision=417278

This commit was manufactured by cvs2svn to create tag
'KDE_3_4_0_RELEASE'.

svn path=/tags/KDE_3_4_0_RELEASE/kdeutils/kdf/; revision=394907

This commit was manufactured by cvs2svn to create tag
'KDE_3_4_0_BETA_2'.

svn path=/tags/KDE_3_4_0_BETA_2/kdeutils/kdf/; revision=386487

This commit was manufactured by cvs2svn to create tag
'KDE_3_4_0_BETA_1'.

svn path=/tags/KDE_3_4_0_BETA_1/kdeutils/kdf/; revision=376088