From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from relay.sgi.com (relay1.corp.sgi.com [137.38.102.111]) by oss.sgi.com (Postfix) with ESMTP id 4FF387F37 for ; Thu, 13 Nov 2014 13:02:58 -0600 (CST) Message-ID: <5465005E.9020106@sgi.com> Date: Thu, 13 Nov 2014 13:02:54 -0600 From: Mark Tinguely MIME-Version: 1.0 Subject: Re: [PATCH 4/9] xfsdump: remove pointless if (dirty); References: <1415818638-32700-1-git-send-email-sandeen@redhat.com> <1415818638-32700-5-git-send-email-sandeen@redhat.com> <5464EBD6.3040107@sgi.com> <5464EEAD.3060500@sandeen.net> In-Reply-To: <5464EEAD.3060500@sandeen.net> List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: xfs-bounces@oss.sgi.com Sender: xfs-bounces@oss.sgi.com To: Eric Sandeen Cc: Eric Sandeen , xfs@oss.sgi.com On 11/13/14 11:47, Eric Sandeen wrote: > On 11/13/14 11:35 AM, Mark Tinguely wrote: >> On 11/12/14 12:57, Eric Sandeen wrote: >>> "dirty" seems to be a remnant of unfinished code; other bits of >>> it are there but commented out, so comment out "if (dirty);" as >>> well, which is a no-op if statement which can't be true. >>> >>> Signed-off-by: Eric Sandeen >>> --- >>> inventory/inv_stobj.c | 2 ++ >>> 1 files changed, 2 insertions(+), 0 deletions(-) >>> >>> diff --git a/inventory/inv_stobj.c b/inventory/inv_stobj.c >>> index becac17..84b15d9 100644 >>> --- a/inventory/inv_stobj.c >>> +++ b/inventory/inv_stobj.c >>> @@ -976,7 +976,9 @@ stobj_delete_mobj(int fd, >>> >>> } >>> free ( mfiles ); >>> +/* >>> if ( dirty ); >>> +*/ >>> } >>> >>> free ( strms ); >> >> Why not remove all the references to dirty in the function? >> Like you said, it doesn't do anything. > > Somebody left this and the rest of the commented-out code there > for some documentation reason, it seems, so I figured... > > It's not like the rest of the code is a thing > of beauty, and this wart is ruining its perfection. ;) > > I have no idea, honestly. xfsdump is dropped in from some alien > world. Somebody @ SGI might know, or could find out by looking > at long-lost history? > > -Eric I will see what I can dig up. We need to start pulling off the warts. The interactive command line parsing is also damaged, I will find the patch and post it. --Mark. _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs