head	1.3;
access;
symbols
	RELEASE_8_3_0:1.3
	RELEASE_9_0_0:1.3
	RELEASE_7_4_0:1.2
	RELEASE_8_2_0:1.2
	RELEASE_6_EOL:1.2
	RELEASE_8_1_0:1.2
	RELEASE_7_3_0:1.2
	RELEASE_8_0_0:1.2
	RELEASE_7_2_0:1.2;
locks; strict;
comment	@# @;


1.3
date	2011.03.19.12.33.55;	author miwi;	state Exp;
branches;
next	1.2;

1.2
date	2009.04.11.09.45.39;	author miwi;	state Exp;
branches;
next	1.1;

1.1
date	2008.12.28.17.07.58;	author miwi;	state Exp;
branches;
next	;


desc
@@


1.3
log
@- Get Rid MD5 support
@
text
@SHA256 (chems-0x04.zip) = 684fcd900c5cf714cb9d92960214de609ffa1fe6493e488a2964222b2645285a
SIZE (chems-0x04.zip) = 377723
@


1.2
log
@- Update to 0x04
@
text
@a0 1
MD5 (chems-0x04.zip) = 391afdc7a4e146079b19893b3c926c14
@


1.1
log
@CHeMS is a free (as in freedom) modular code-driven content helper
management system (the first!) written in PHP fully compliant with
the XHTML 1.1 and CSS2 standards. One of its main purpose is to help
developers and (not so) advanced users to easily setting up a web
application (blog, site, etc.) without have to deal with the "boring"
side of this process such as layout generation code, menu blocks and
so on. Its modularization system allow to mantain a light and fast core
which only have to generate the layout and load the modules to delegate
all the real and hard work to them. You never have to learn new weird
APIs in order to deal with the CHeMS internals, there is full controll.
That's why CHeMS is not a Content Management System (CMS) but rather it's
an assistant.

WWW:	http://chems.sf.net
@
text
@d1 3
a3 3
MD5 (chems-0x03_1.zip) = 00614d9132e65366fb744009d7549948
SHA256 (chems-0x03_1.zip) = 8c35fcecf299348261e22dff1b211d975351cbb01fd7e5b61ca273ac877dd06e
SIZE (chems-0x03_1.zip) = 116002
@

