--===============0139718556==
Content-Type: multipart/signed;
  boundary="nextPart3262818.kByFNJFqEi";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart3262818.kByFNJFqEi
Content-Type: text/plain;
  charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Wednesday 09 March 2005 17:01, Aaron Meder wrote:
> hmm?
> any solutions?

I already told the reasons and a solution: use a local test server and=20
upload only when you really need.=20
Or use a CVS server and set up the web server to get the files from CVS=20
from time to time, so when you commit to the CVS the files will be=20
visible by accessing the web page. This is the recommended way to=20
develop in a team.

Andras

=2D-=20
Quanta Plus developer - http://quanta.sourceforge.net
K Desktop Environment - http://www.kde.org

--nextPart3262818.kByFNJFqEi
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQBCL04nTQdfac6L/08RAgLBAKCgLS7/KJsRsg8htrFQEprePoKksACeNB77
QkJSNonpHNgNzuSQeVa5iq4=
=QxjD
-----END PGP SIGNATURE-----

--nextPart3262818.kByFNJFqEi--


--===============0139718556==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Quanta mailing list
Quanta@mail.kde.org
https://mail.kde.org/mailman/listinfo/quanta

--===============0139718556==--