From: Joel Brobecker <brobecker@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: vapier@gentoo.org, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdbserver: start a gitignore
Date: Wed, 22 Dec 2010 14:43:00 -0000 [thread overview]
Message-ID: <20101222131237.GL2596@adacore.com> (raw)
In-Reply-To: <E1PVMnq-00047S-4X@fencepost.gnu.org>
> How long can it be? Something like *.o, *.so, *.exe, and a couple of
> binaries we produce? Is that really a problem?
I'm not really objecting, nor am I thinking that the list of overly
long. If others are happy with that, that's fine with me too. Note
that you'll also want to add all the files generated during the
configure and build: config.xxx, Makefile, etc.
--
Joel
next prev parent reply other threads:[~2010-12-22 13:12 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
2010-12-22 5:32 ` Yao Qi
2010-12-22 11:24 ` Eli Zaretskii
2010-12-22 14:43 ` Joel Brobecker [this message]
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=20101222131237.GL2596@adacore.com \
--to=brobecker@adacore.com \
--cc=eliz@gnu.org \
--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