From: Martin Man <Martin.Man@...>
Date: 2002-02-05T17:28:53+09:00
Subject: Re: CVS commit emails


--Qxx1br4bt0+wmkIi
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Feb 05, 2002 at 05:00:43PM +0900, Yukihiro Matsumoto wrote:
> Hi,
>=20
> In message "CVS commit emails"
>     on 02/02/05, Martin Man <Martin.Man@seznam.cz> writes:
>=20
> |1) they send only one email for one commit (not one for each set of modi=
fied=20
> |files in different directories), so that one commit email means one chun=
k of
> |related changes.
>=20
> This is my fault;  I'm using pcl-cvs Emacs package, and it commits for
> each directories separately.  If someone knows to fix this, tell me.
>=20

I don't think it's fault of pcl-cvs, this just happen to be default behavior
of cvs, the solution is to put some magic scripts to the CVSROOT that are a=
ble
to merge consecutive commit results in one resulting email...

> |2) they attach context diffs of all changes to the bottom of email so th=
at one
> |can immediately see what has happened with the sources.
>=20
> If you have fulltime connectivity, you have no problem.  If you don't,
> hmm, what do you guys feel about this?  Especially, knu?

anyway even if you do have the connectivity, via the links provided you=20
can see current revisions of files, but not the changes that were made=20
(at least not directly via these links, if I'm not mistaken)...
>=20
> 							matz.
>=20

martin

--=20
1024D/6E060223    2CC0 4AF6 92DA 5CBF 5F09  7BCB 6202 7024 6E06 0223
http://mman.dyndns.org/mman.gpg

--Qxx1br4bt0+wmkIi
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8X5ddYgJwJG4GAiMRAqp9AJ0ThoYTE6IasadQG7yGkLQ+armb5wCfY7TG
XBsxiq00yQKs+0EtjPwXh3Q=
=1iXg
-----END PGP SIGNATURE-----

--Qxx1br4bt0+wmkIi--