From: Jim Blandy <jimb@codesourcery.com>
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 14:54:00 -0000 [thread overview]
Message-ID: <m3irfs3ykg.fsf@codesourcery.com> (raw)
In-Reply-To: <20061231143237.GA3428@adacore.com> (Joel Brobecker's message of "Sun, 31 Dec 2006 18:32:37 +0400")
Joel Brobecker <brobecker@adacore.com> writes:
>> > 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.
Mistakes in Joel's suggested new procedure would be caught by CVS ---
another point in its favor.
next prev parent reply other threads:[~2006-12-31 14:54 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 [this message]
2006-12-31 15:19 ` Daniel Jacobowitz
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=m3irfs3ykg.fsf@codesourcery.com \
--to=jimb@codesourcery.com \
--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