Linux Container Development
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: Nathan Lynch <ntl-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
	Sukadev Bhattiprolu
	<sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Subject: Re: [cr_tests] warning fixes and build system changes
Date: Mon, 15 Feb 2010 10:25:33 -0600	[thread overview]
Message-ID: <20100215162533.GA4153@us.ibm.com> (raw)
In-Reply-To: <1266250490.6542.6.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>

Quoting Nathan Lynch (ntl-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org):
> On Mon, 2010-02-15 at 09:47 -0600, Serge E. Hallyn wrote:
> 
> > Was it on purpose that you no longer delete the cr_* directories
> > with the test results on a 'make clean'?  If you're concerned about
> > accidentally losing info, then how about adding 'make distclean'
> > to do that?
> 
> There is a "testclean" target which does this.  The changelog notes this
> change in behavior.

Oops.

thanks,
-serge

      parent reply	other threads:[~2010-02-15 16:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-11 23:17 [cr_tests] warning fixes and build system changes Nathan Lynch
     [not found] ` <1265930227.17626.3313.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2010-02-12 14:25   ` Serge E. Hallyn
2010-02-15 15:47   ` Serge E. Hallyn
     [not found]     ` <20100215154751.GA2482-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-02-15 16:14       ` Nathan Lynch
     [not found]         ` <1266250490.6542.6.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2010-02-15 16:25           ` Serge E. Hallyn [this message]

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=20100215162533.GA4153@us.ibm.com \
    --to=serue-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=ntl-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org \
    --cc=sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
    /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