public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] xfsprogs: Make the compile output cleaner V2
Date: Thu, 14 Jan 2010 09:30:01 +1100	[thread overview]
Message-ID: <20100113223001.GR17483@discord.disaster> (raw)
In-Reply-To: <20100113220814.GA17310@infradead.org>

On Wed, Jan 13, 2010 at 05:08:14PM -0500, Christoph Hellwig wrote:
> On Wed, Jan 13, 2010 at 09:03:27PM +1100, Dave Chinner wrote:
> > -LDIRT = config.log .dep config.status config.cache confdefs.h conftest* \
> > +DISTDIRT = config.log .dep config.status config.cache confdefs.h conftest* \
> >  	built .census install.* install-dev.* *.gz autom4te.cache/* libtool \
> >  	include/builddefs include/platform_defs.h
> 
> >  distclean: clean
> > -	rm -f $(LDIRT)
> > +	$(Q)rm -f $(DISTDIRT)
> 
> What does this have to do with the rest?

That's the "make clean doesn't cause configure to run again" fix.

> Otherwise looks good,
> 
> 
> Reviewed-by: Christoph Hellwig <hch@lst.de>
> 
> Any chance you could also port it to xfsdump?

Yes, I'm slowly working my way through the different trees
doing this, then I'll go fix all the compile warnings we
currently have...

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2010-01-13 22:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-13 10:03 [PATCH] xfsprogs: Make the compile output cleaner V2 Dave Chinner
2010-01-13 14:50 ` Eric Sandeen
2010-01-13 22:08 ` Christoph Hellwig
2010-01-13 22:30   ` Dave Chinner [this message]
2010-01-14  6:51     ` Christoph Hellwig
2010-01-14 10:11       ` Dave Chinner
2010-01-17 11:55         ` Christoph Hellwig
2010-01-13 22:43   ` Alex Elder

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100113223001.GR17483@discord.disaster \
    --to=david@fromorbit.com \
    --cc=hch@infradead.org \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox