From mboxrd@z Thu Jan 1 00:00:00 1970 From: Otavio Salvador Subject: Re: [PATCH][XM] Extend width of ID to 5. Date: Fri, 20 Apr 2007 10:17:17 -0300 Message-ID: <87k5w7yyle.fsf@lab.ossystems.com.br> References: <907625E08839C4409CE5768403633E0B018E1C32@sefsexmb1.amd.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: In-Reply-To: <907625E08839C4409CE5768403633E0B018E1C32@sefsexmb1.amd.com> (Mats Petersson's message of "Fri, 20 Apr 2007 15:13:49 +0200") List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Petersson, Mats" Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org "Petersson, Mats" writes: >> The only thing it can mess is automated tests and routines that uses >> the fixed width and will need a fix after this patch gets in. > > Yes, of course, but such scrips would also be broken when the numbers > get too big to fit in the fields, so those scripts are already possibly > broken. Any script that parses the output of a program (and wishes to > remain functional after revisions of the software) should use flexible > field parsing rather than column-grabbing, in my opinion. Sure, I agree completely with you while I also know that this kind of "not-so-well-written-script" exist ;-) > But it's also why I suggested that it may go into unstable only, rather > than into the near-release 3.0.5 tree. Well, I just think that a note on release notes would solve that. -- Otavio Salvador O.S. Systems E-mail: otavio@ossystems.com.br http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br