--DocE+STaALJfprDB
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Dec 06, 2002 at 06:24:55PM +0100, Jaromir Dolecek wrote:
> Jason R. Fink wrote:
> > > But isn't it convenient?=20
> >=20
> > I am sure it is, so, I guess my question is,
> > if we add an option to a utility that is conformant,
> > does that break conformance? If it doesn't, then I will
> > play with adding -v and get the PR closed.
>=20
> 'Conforms' means that options which are in standard are implemented
> in our utility, and that they work according to standard. You can
> add additional flags and stay conformant.
>=20
> cp -v would be handy occassionally.

Please enlighten me...

Wouldn't a script expecting a standard-conforming cp expect that
``cp -v foo'' copies the file ``-v'' to the file ``foo'' ?

	-is

--=20
seal your e-mail: http://www.gnupg.org/

--DocE+STaALJfprDB
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (NetBSD)

iD8DBQE98PpnPCRcZ/VMtk4RAk+eAJwPJiqx4rbcw+2f1ROpBjIyWa69BQCdH9B9
PP2joouxI7gnoX04ac4zK2M=
=txMK
-----END PGP SIGNATURE-----

--DocE+STaALJfprDB--