[Cvs-dev] Re: cvs-chpass.patch (former: cvs-passwd.patch)

[Derek R. Price]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Tony Hoyle wrote:
> Prasad J Pandit wrote:
>>   Exactly! I too thought the same way. But then changed it from
>> 'passwd' to 'chpass', thinking that, as long as facility is provided
>> to change the password, it doesn't matter much, what the name of the
>> command is.

Actually, I was following your conversation and I probably should have
said something at the time, but I thought that this response of yours
was based on a misunderstanding of what Mark was recommending.

> It's the client/server protocol that really matters.. the cvsnt clients
> will be sending 'passwd' so changing it to 'chpass' breaks the
> communication (yes I could eventually make the cvsnt clients send chpass
> too but people rarely update clients - all the existing ones wouldn't
> work.. if we can avoid that happening it's a result).

I agree that it is better to maintain interoperability by supporting the
same protocol.  Since CVSNT has a passwd command and there is some
overlap in functionality, it would be good to work with it as much as
possible, even if every piece of functionality is not offered by both
servers.

Regards,

Derek
- --
Derek R. Price
CVS Solutions Architect
Get CVS support at Ximbiot <http://ximbiot.com>!
v: +1 248.835.1260
f: +1 248.835.1263
<mailto:address@hidden>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEmUv6LD1OTBfyMaQRArweAJ4oI+OywPF+DVYzIgF0sX82vyFygQCfUhP6
mf2p6baUizk1rVloPAoDlyI=
=Awpa
-----END PGP SIGNATURE-----