From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15893 invoked by alias); 22 Dec 2010 11:24:28 -0000 Received: (qmail 15885 invoked by uid 22791); 22 Dec 2010 11:24:27 -0000 X-SWARE-Spam-Status: No, hits=-1.1 required=5.0 tests=AWL,BAYES_20,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from fencepost.gnu.org (HELO fencepost.gnu.org) (140.186.70.10) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 22 Dec 2010 11:24:23 +0000 Received: from eliz by fencepost.gnu.org with local (Exim 4.69) (envelope-from ) id 1PVMnq-00047S-4X; Wed, 22 Dec 2010 06:24:18 -0500 From: Eli Zaretskii To: Joel Brobecker CC: vapier@gentoo.org, gdb-patches@sourceware.org In-reply-to: <20101222044518.GJ2596@adacore.com> (message from Joel Brobecker on Wed, 22 Dec 2010 08:45:18 +0400) Subject: Re: [PATCH] gdbserver: start a gitignore Reply-to: Eli Zaretskii References: <1292416368-24885-1-git-send-email-vapier@gentoo.org> <20101222044518.GJ2596@adacore.com> Message-Id: Date: Wed, 22 Dec 2010 11:24:00 -0000 X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2010-12/txt/msg00391.txt.bz2 > Date: Wed, 22 Dec 2010 08:45:18 +0400 > From: Joel Brobecker > 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? I see such exclusions in every GNU project I'm working on. I don't think this road is too long ;-) > I believe that we should encourage people to compile GDB using > a build directory that is different from the source directory. Right, but you cannot (and shouldn't, IMO) force people doing that by such measures. People who want to build in the source tree will complain, but will not stop doing that. > Except I don't know why I think that! :-). I do. From gdb/README: You can build GDB right in the source directory: cd gdb-VERSION ./configure make cp gdb/gdb /usr/local/bin/gdb (or wherever you want) However, we recommend that an empty directory be used instead. This way you do not clutter your source tree with binary files and will be able to create different builds with different configuration options.