From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13914 invoked by alias); 5 Oct 2009 17:23:13 -0000 Received: (qmail 13905 invoked by uid 22791); 5 Oct 2009 17:23:13 -0000 X-SWARE-Spam-Status: No, hits=-0.5 required=5.0 tests=AWL,BAYES_00,URIBL_BLACK X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 05 Oct 2009 17:23:09 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id B82CC2BAC18; Mon, 5 Oct 2009 13:23:07 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id QDcOB8eycoN9; Mon, 5 Oct 2009 13:23:07 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 81F432BAC16; Mon, 5 Oct 2009 13:23:06 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id 851ECF5921; Mon, 5 Oct 2009 10:23:03 -0700 (PDT) Date: Mon, 05 Oct 2009 17:23:00 -0000 From: Joel Brobecker To: Doug Evans Cc: gdb@sourceware.org Subject: Re: sim/common/version.in? Message-ID: <20091005172303.GF29600@adacore.com> References: <20091005160706.A15356E3D9@sebabeach.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091005160706.A15356E3D9@sebabeach.org> User-Agent: Mutt/1.5.18 (2008-05-17) Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2009-10/txt/msg00082.txt.bz2 > A cronjob could periodically update src/sim/common/version.in from > src/gdb/version.in, for example. That would still leave updating the > file for releases, but if there was a script that was run to help prep > a release, it could also copy src/gdb/version.in to > src/sim/common/version.in. The release process is a collection of scripts, so adding that extra step would mean updating the scripts once. I'm also fine either way. Gdbserver is in the same situation; it can be configured independently of GDB, but still needs access to the GDB sources. -- Joel