--===============0930870552==
Content-Type: multipart/signed;
  boundary="nextPart12825207.Qqm5HW5CCy";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart12825207.Qqm5HW5CCy
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Thursday 21 December 2006 19:30, Sushant Tambare wrote:
> hey Andres but I think each time using CVS is not the proper way to do the
> task or source code versioning....
> It will relate to versioning of the files...
> sushant

Yes, this is correct. CVS or SVN are about allowing the developer to work a=
t=20
the same time on a project. If you want to have versioning you have to read=
=20
more in the docs how to do this in CVS or SVN. Basicly you copy the code, i=
f=20
you want to have a new version, into a new branch and then you can work on=
=20
the released version and the development version at the same time.
I really encourage you to read more about the beauty of SVN and CVS, they c=
an=20
really help you with your problem.

Jens

--nextPart12825207.Qqm5HW5CCy
Content-Type: application/pgp-signature

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

iD8DBQBFiz9IkYmIVB8IV+ARAl7dAJ9GB8Qj4qA7UYwek8egmU4TUREsrgCdH3Tk
jUdWTmZ5PgdQWighUv1mXeQ=
=fYTJ
-----END PGP SIGNATURE-----

--nextPart12825207.Qqm5HW5CCy--

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

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

--===============0930870552==--