Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>, gdb-patches@sourceware.org
Subject: Re: [RFA/testsuite/ada] re-implement make clean & distclean
Date: Sun, 31 Dec 2006 15:19:00 -0000	[thread overview]
Message-ID: <20061231151853.GD16449@nevyn.them.org> (raw)
In-Reply-To: <20061231143237.GA3428@adacore.com>

On Sun, Dec 31, 2006 at 06:32:37PM +0400, Joel Brobecker wrote:
> > > 2006-12-31  Joel Brobecker  <brobecker@adacore.com>
> > > 
> > >         * gdb.ada/Makefile.in (EXECUTABLES): Delete.
> > >         (MISCELLANEOUS): Delete.
> > >         (clean): Re-implement.
> > >         (mostlyclean): Likewise.
> > > 
> > > Tested on my x86-linux laptop.  Any objection?
> > 
> > Hmm, seems a bit scary to me.  If I read this correctly, a file named
> > NOTES would be wiped isn't it?  I'm using a seperate object dir, so I
> > probably won't care, but others might...
> 
> The thing is that we very rarely add files other than the exp files
> and the source code. If we add a file called NOTES in gdb.ada, then
> we can adjust the exclusion list in the find command. Doing it the
> other way around is a lot more work.

Except that, like Mark implies, I tend to keep my notes in my working
directory.  If I'm debugging a bunch of testcases and I needed to keep
notes about what was going on, I'd be quite surprised if make clean
deleted my notes!

I don't object too strongly, though, if others like this approach.
I wouldn't put them in that directory anyway, just in gdb/testsuite/.

-- 
Daniel Jacobowitz
CodeSourcery


  parent reply	other threads:[~2006-12-31 15:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-31 10:08 Joel Brobecker
2006-12-31 13:12 ` Mark Kettenis
2006-12-31 14:31   ` Joel Brobecker
2006-12-31 14:54     ` Jim Blandy
2006-12-31 15:19     ` Daniel Jacobowitz [this message]
2006-12-31 15:27       ` Joel Brobecker
2006-12-31 18:05         ` Daniel Jacobowitz
2007-01-01 14:14           ` Joel Brobecker

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=20061231151853.GD16449@nevyn.them.org \
    --to=drow@false.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    /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