From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2117 invoked by alias); 6 Nov 2013 07:08:25 -0000 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 Received: (qmail 2106 invoked by uid 89); 6 Nov 2013 07:08:24 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=2.6 required=5.0 tests=AWL,BAYES_40,GARBLED_BODY,RDNS_NONE autolearn=no version=3.3.2 X-HELO: relay1.mentorg.com Received: from Unknown (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 06 Nov 2013 07:08:23 +0000 Received: from svr-orw-fem-01.mgc.mentorg.com ([147.34.98.93]) by relay1.mentorg.com with esmtp id 1VdxDj-0006pd-Gb from Yao_Qi@mentor.com ; Tue, 05 Nov 2013 23:08:07 -0800 Received: from SVR-ORW-FEM-04.mgc.mentorg.com ([147.34.97.41]) by svr-orw-fem-01.mgc.mentorg.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Tue, 5 Nov 2013 23:08:07 -0800 Received: from qiyao.dyndns.org (147.34.91.1) by svr-orw-fem-04.mgc.mentorg.com (147.34.97.41) with Microsoft SMTP Server id 14.2.247.3; Tue, 5 Nov 2013 23:08:06 -0800 Message-ID: <5279EA7E.1090609@codesourcery.com> Date: Wed, 06 Nov 2013 07:56:00 -0000 From: Yao Qi User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130110 Thunderbird/17.0.2 MIME-Version: 1.0 To: Eli Zaretskii CC: Subject: Re: [PATCH 04/10] Don't stress 'remote' in "Data Caching" in doc References: <1383458049-20893-1-git-send-email-yao@codesourcery.com> <1383458049-20893-5-git-send-email-yao@codesourcery.com> <83k3gpa0hf.fsf@gnu.org> In-Reply-To: <83k3gpa0hf.fsf@gnu.org> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8bit X-IsSubscribed: yes X-SW-Source: 2013-11/txt/msg00107.txt.bz2 On 11/04/2013 12:55 AM, Eli Zaretskii wrote: > Thanks. But may I ask in the future not to split the patches to > documentation that are related to the same series? When you split > them, it makes the review harder, as I see the documentation changes > piecemeal, rather than together. What I want is to keep doc in sync with the code in every change/patch. I'll put all doc stuff in a single patch from now on. Sorry for the inconvenience. -- Yao (齐尧)