From: Joel Brobecker <brobecker@adacore.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdbserver: start a gitignore
Date: Wed, 22 Dec 2010 04:45:00 -0000 [thread overview]
Message-ID: <20101222044518.GJ2596@adacore.com> (raw)
In-Reply-To: <1292416368-24885-1-git-send-email-vapier@gentoo.org>
> diff --git a/gdb/gdbserver/.gitignore b/gdb/gdbserver/.gitignore
> new file mode 100644
> index 0000000..9c94950
> --- /dev/null
> +++ b/gdb/gdbserver/.gitignore
> @@ -0,0 +1,4 @@
> +gdbreplay
> +gdbserver
> +reg-*.c
> +version.c
I'm OK but slightly hesitant to introduce a .gitignore for files that
are compilation artifacts, not development artifacts. If we start
on that road, the list is possibly quite long.
I believe that we should encourage people to compile GDB using
a build directory that is different from the source directory.
Except I don't know why I think that! :-). I know that I have been
told that this should be the cannonical way of building GNU projects,
and that the in-source build might one day become unsupported.
I just know that I find it more convenient, precisely because
it avoids polluting my source tree with such build artifacts.
What do people think?
--
Joel
next prev parent reply other threads:[~2010-12-22 4:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-15 12:33 Mike Frysinger
2010-12-22 4:45 ` Joel Brobecker [this message]
2010-12-22 5:32 ` Yao Qi
2010-12-22 11:24 ` Eli Zaretskii
2010-12-22 14:43 ` Joel Brobecker
2010-12-22 18:17 ` Mike Frysinger
2010-12-23 4:22 ` Joel Brobecker
2010-12-24 2:55 ` Mike Frysinger
2010-12-22 22:05 ` Michael Snyder
2010-12-23 3:19 ` Mike Frysinger
2010-12-22 15:58 ` Tom Tromey
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=20101222044518.GJ2596@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=vapier@gentoo.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