From: Mike Frysinger <vapier@gentoo.org>
To: Michael Snyder <msnyder@vmware.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
Joel Brobecker <brobecker@adacore.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] gdbserver: start a gitignore
Date: Thu, 23 Dec 2010 03:19:00 -0000 [thread overview]
Message-ID: <201012222225.37336.vapier@gentoo.org> (raw)
In-Reply-To: <4D124727.3070504@vmware.com>
[-- Attachment #1: Type: Text/Plain, Size: 703 bytes --]
On Wednesday, December 22, 2010 13:44:55 Michael Snyder wrote:
> Eli Zaretskii wrote:
> >> Date: Wed, 22 Dec 2010 08:45:18 +0400
> >> From: Joel Brobecker <brobecker@adacore.com>
> >> Cc: gdb-patches@sourceware.org
> >>
> >> 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.
> >
> > How long can it be? Something like *.o, *.so, *.exe, and a couple of
> > binaries we produce? Is that really a problem?
>
> *.a, *.la, *.lo....
... which are already handled in the top level and thus not relevant to gdb-
specific gitignore files
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2010-12-23 2:26 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
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 [this message]
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=201012222225.37336.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.com \
/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