X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C8A1A0.6CE44260@onstor-exch02.onstor.net>; Fri, 18 Apr 2008 15:06:17 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8A1A0.6CE44260"
Content-class: urn:content-classes:message
Subject: RE: 23441 	[Cougar] domain add / domain modify allow repeated options 
Date: Fri, 18 Apr 2008 15:06:17 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E097CC909@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: 23441 	[Cougar] domain add / domain modify allow repeated options 
Thread-Index: AcihnFTzrKtgyAAhS8SILmI0yFGMNwAA9LZw
From: "Maxim Kozlovsky" <maxim.kozlovsky@onstor.com>
To: "Maxim Kozlovsky" <maxim.kozlovsky@onstor.com>,
	"dl-Cougar" <dl-Cougar@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8A1A0.6CE44260
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

As an example of some accepted standard, try
http://www.opengroup.org/onlinepubs/007908775/xbd/utilconv.html#usg. It
specifies what should happen when an option is specified multiple times,
but never says the specifying an option multiple times should be
prohibited.

_____________________________________________
From: Maxim Kozlovsky=20
Sent: Friday, April 18, 2008 2:37 PM
To: dl-Cougar
Subject: 23441 [Cougar] domain add / domain modify allow repeated
options=20

Hello,

I have seen a few similar defects filed where the complain is that an
option can be specified multiple times. Who is coming up with those
rules and where are these rules specified? Allowing specifying the same
option multiple times is quite common practice at least in Linux and in
Windows, try almost any of utilities (don't know about Mac, but who
cares about them anyway). The multiple options are usually resolved by
the last one taking precedence. It is convenient as well. If you are
typing a long command string, and make a mistake in the beginning you
can simply enter an option again.

Max

------_=_NextPart_001_01C8A1A0.6CE44260
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7653.38">
<TITLE>RE: 23441 	[Cougar] domain add / domain modify allow repeated =
options </TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">As an example of some accepted =
standard, try</FONT></SPAN><SPAN LANG=3D"en-us"> </SPAN><A =
HREF=3D"http://www.opengroup.org/onlinepubs/007908775/xbd/utilconv.html#u=
sg"><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><U><FONT =
COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">http://www.opengroup.org/onlinepubs/007908775/xbd/utilconv=
.html#usg</FONT></U></SPAN><SPAN LANG=3D"en-us"></SPAN></A><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" =
SIZE=3D2 FACE=3D"Arial">. It specifies what should happen when an option =
is specified multiple times, but never says the specifying an option =
multiple times should be prohibited.</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
SIZE=3D2 =
FACE=3D"Tahoma">_____________________________________________<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">From:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> Maxim Kozlovsky<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">Sent:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> Friday, April 18, 2008 =
2:37 PM<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">To:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> dl-Cougar<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">Subject:</FONT></B></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma"> 23441 [Cougar] domain add / domain modify allow =
repeated options</FONT></SPAN><SPAN LANG=3D"en-us"> </SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
SIZE=3D2 FACE=3D"Arial">Hello,</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">I have =
seen a few similar defects filed where the complain is that an option =
can be specified multiple times. Who is coming up with those rules and =
where are these rules specified? Allowing specifying the same option =
multiple times is quite common practice at least in Linux and in =
Windows, try almost any of utilities (don&#8217;t know about Mac, but =
who cares about them anyway). The multiple options are usually resolved =
by the last one taking precedence. It is convenient as well. If you are =
typing a long command string, and make a mistake in the beginning you =
can simply enter an option again.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Max</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

</BODY>
</HTML>
------_=_NextPart_001_01C8A1A0.6CE44260--
