From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Mike Frysinger'" <vapier@gentoo.org>, <gdb-patches@sourceware.org>
Subject: RE: [PATCH] gdb: start a gitignore
Date: Tue, 29 Mar 2011 08:22:00 -0000 [thread overview]
Message-ID: <004a01cbede5$1e157ed0$5a407c70$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <1301367964-6823-1-git-send-email-vapier@gentoo.org>
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.
Putting the build directory in git seems like something strange to me...
Does your patch means that there are some subdirectories that
do not require to use a separate build directory?
Pierre Muller
GDB pascal language maintainer.
> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Mike Frysinger
> Envoyé : mardi 29 mars 2011 05:06
> À : gdb-patches@sourceware.org
> Objet : [PATCH] gdb: start a gitignore
>
> Signed-off-by: Mike Frysinger <vapier@gentoo.org>
>
> 2011-03-28 Mike Frysinger <vapier@gentoo.org>
>
> * .gitignore: New file.
> ---
> gdb/.gitignore | 17 +++++++++++++++++
> 1 files changed, 17 insertions(+), 0 deletions(-)
> create mode 100644 gdb/.gitignore
>
> diff --git a/gdb/.gitignore b/gdb/.gitignore
> new file mode 100644
> index 0000000..ea3a4f9
> --- /dev/null
> +++ b/gdb/.gitignore
> @@ -0,0 +1,17 @@
> +/version.c
> +/xml-builtin.c
> +
> +/ada-exp.c
> +/ada-lex.c
> +/c-exp.c
> +/cp-name-parser.c
> +/f-exp.c
> +/gdb
> +/gdbtui
> +/init.c
> +/jv-exp.c
> +/m2-exp.c
> +/objc-exp.c
> +/observer.h
> +/observer.inc
> +/p-exp.c
> --
> 1.7.4.1
next prev parent reply other threads:[~2011-03-29 7:54 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 [this message]
2011-03-29 10:12 ` André Pönitz
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='004a01cbede5$1e157ed0$5a407c70$@muller@ics-cnrs.unistra.fr' \
--to=pierre.muller@ics-cnrs.unistra.fr \
--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