From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31015 invoked by alias); 9 May 2012 16:30:44 -0000 Received: (qmail 31003 invoked by uid 22791); 9 May 2012 16:30:43 -0000 X-SWARE-Spam-Status: No, hits=-6.4 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 09 May 2012 16:30:30 +0000 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q49GUUov020580 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 9 May 2012 12:30:30 -0400 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id q49GUSVL016423 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 9 May 2012 12:30:29 -0400 From: Tom Tromey To: Giuseppe MONTALTO Cc: "gdb-patches\@sourceware.org" Subject: Re: [PATCH] new MI command for pattern filling of memory regions References: <76FE3225DF13124EA2D05B290B624C95E65F2D466E@SAFEX1MAIL1.st.com> Date: Wed, 09 May 2012 16:30:00 -0000 In-Reply-To: <76FE3225DF13124EA2D05B290B624C95E65F2D466E@SAFEX1MAIL1.st.com> (Giuseppe MONTALTO's message of "Wed, 9 May 2012 18:18:27 +0200") Message-ID: <8762c5tizf.fsf@fleche.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.95 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain 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: 2012-05/txt/msg00283.txt.bz2 >>>>> "Giuseppe" == Giuseppe MONTALTO writes: Giuseppe> it's the first time I attempt a contribution to gdb, so feel Giuseppe> free to ask for details and, please, let me know if I'm doing Giuseppe> anything wrong! Do you have a copyright assignment set up? If not, let me know and we can get you started. This must be completed before we can accept a patch. I didn't review the patch. I think it is probably better to get the copyright stuff sorted out first. I did notice that the patch doesn't include a documentation change. All new MI commands must be documented. Tom