Tags

update VERSIONSTRING and pbconf files for tag 2.4.0 rc1.

update VERSIONSTRING and pbconf files for tag 2.3.0.

update VERSIONSTRING and pbconf files for tag 2.3.0 rc1.

update VERSIONSTRING and pbconf files for tag 2.2.0.

update VERSIONSTRING and pbconf files for tag 2.2.0 rc3.

update VERSIONSTRING and pbconf files for tag 2.2.0 rc2.

update VERSIONSTRING and pbconf files for tag 2.2.0 rc1.

update VERSIONSTRING and pbconf files for tag 2.1.1

Version number type error.

revert svn 6250

update VERSIONSTRING and pbconf files for tag 2.1.0~rc2.

update pbconf files for tag 2.1.0~rc1

changed notification to be more informative & less confusing to the installer.

Move the various /pbconf/tags/ directories'\'' contents into the coresponding /branches/ (when available) or /tags/ directory, creating a new '\''packaging'\'' subdirectory within the tag or branch if it did not already exist.  Note that, since these are all ex post facto moves of files into an existing tag or branch, they probably will not actually work with the code on that tag or branch.  However we want to preserve the original pbconf configuration, thus we'\''ll keep them there

Move the various /pbconf/tags/ directories'\'' contents into the coresponding /branches/ (when available) or /tags/ directory, creating a new '\''packaging'\'' subdirectory within the tag or branch if it did not already exist.  Note that, since these are all ex post facto moves of files into an existing tag or branch, they probably will not actually work with the code on that tag or branch.  However we want to preserve the original pbconf configuration, thus we'\''ll keep them there

Move the various /pbconf/tags/ directories'\'' contents into the coresponding /branches/ (when available) or /tags/ directory, creating a new '\''packaging'\'' subdirectory within the tag or branch if it did not already exist.  Note that, since these are all ex post facto moves of files into an existing tag or branch, they probably will not actually work with the code on that tag or branch.  However we want to preserve the original pbconf configuration, thus we'\''ll keep them there

Move the various /pbconf/tags/ directories'\'' contents into the coresponding /branches/ (when available) or /tags/ directory, creating a new '\''packaging'\'' subdirectory within the tag or branch if it did not already exist.  Note that, since these are all ex post facto moves of files into an existing tag or branch, they probably will not actually work with the code on that tag or branch.  However we want to preserve the original pbconf configuration, thus we'\''ll keep them there

tag the state of the fossology trunk as it exists at svn 5913, immediately prior to copying the contents of branches/fossology2.0 into trunk

changed version string to reflect rc3

changed version string to reflect rc2