From: "André Pönitz" <andre.poenitz@nokia.com>
To: gdb-patches@sourceware.org
Cc: ext Pierre Muller <pierre.muller@ics-cnrs.unistra.fr>,
"'Mike Frysinger'" <vapier@gentoo.org>
Subject: Re: [PATCH] gdb: start a gitignore
Date: Tue, 29 Mar 2011 10:12:00 -0000 [thread overview]
Message-ID: <201103291011.05247.andre.poenitz@nokia.com> (raw)
In-Reply-To: <004a01cbede5$1e157ed0$5a407c70$@muller@ics-cnrs.unistra.fr>
On Tuesday 29 March 2011 09:44:21 ext Pierre Muller wrote:
> I am not sure I understand the reason of these patches:
>
> all the listed files are always generated in the build directory,
> and gdb should never be build in its source directory
> so that you should never end up by creating those in
> a source directory.
gdb builds just fine within the source directory, and especially with git's
ability to do a proper cleanup of the source directory (git clean -dxf) there
is not much of a reason to use shadow builds (unless one really wants
to build different configurations from the _same_ source).
Andre'
next prev parent reply other threads:[~2011-03-29 8:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-29 5:02 Mike Frysinger
2011-03-29 8:22 ` Pierre Muller
2011-03-29 10:12 ` André Pönitz [this message]
2011-03-29 15:48 ` 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=201103291011.05247.andre.poenitz@nokia.com \
--to=andre.poenitz@nokia.com \
--cc=gdb-patches@sourceware.org \
--cc=pierre.muller@ics-cnrs.unistra.fr \
--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