From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22319 invoked by alias); 24 Jul 2009 19:18:47 -0000 Received: (qmail 22310 invoked by uid 22791); 24 Jul 2009 19:18:46 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx2.redhat.com (HELO mx2.redhat.com) (66.187.237.31) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 24 Jul 2009 19:18:38 +0000 Received: from int-mx2.corp.redhat.com (int-mx2.corp.redhat.com [172.16.27.26]) by mx2.redhat.com (8.13.8/8.13.8) with ESMTP id n6OJIXud007387; Fri, 24 Jul 2009 15:18:33 -0400 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx2.corp.redhat.com (8.13.1/8.13.1) with ESMTP id n6OJIWvg019739; Fri, 24 Jul 2009 15:18:32 -0400 Received: from opsy.redhat.com (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id n6OJIUAN002965; Fri, 24 Jul 2009 15:18:31 -0400 Received: by opsy.redhat.com (Postfix, from userid 500) id BCDCD3782AF; Fri, 24 Jul 2009 13:18:30 -0600 (MDT) To: Eli Zaretskii Cc: Reid Kleckner , gdb-patches@sourceware.org, unladen-swallow@googlegroups.com Subject: Re: [RFA] Add interface for registering JITed code References: <9a9942200907221615o570e749fh5cb186c1600f159c@mail.gmail.com> <9a9942200907240946q1546646ft6e9112f263bcefdf@mail.gmail.com> <83iqhh52un.fsf@gnu.org> From: Tom Tromey Reply-To: Tom Tromey Date: Fri, 24 Jul 2009 20:55:00 -0000 In-Reply-To: <83iqhh52un.fsf@gnu.org> (Eli Zaretskii's message of "Fri\, 24 Jul 2009 21\:54\:08 +0300") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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: 2009-07/txt/msg00605.txt.bz2 >>>>> "Eli" == Eli Zaretskii writes: Eli> Unfortunately, the NEWS entry is not instrumental enough. It doesn't Eli> tell the user how to use the feature. Is it possible to come up with Eli> a more useful entry? I think the NEWS entry is fine. The feature works automatically. Users need do nothing. Tom