From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-62745-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 7560 invoked by alias); 8 Apr 2009 06:55:34 -0000
Received: (qmail 7550 invoked by uid 22791); 8 Apr 2009 06:55:34 -0000
X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 	tests=AWL,BAYES_00,SPF_SOFTFAIL
X-Spam-Check-By: sourceware.org
Received: from mtaout2.012.net.il (HELO mtaout2.012.net.il) (84.95.2.4)     by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 08 Apr 2009 06:55:25 +0000
Received: from conversion-daemon.i_mtaout2.012.net.il by i_mtaout2.012.net.il (HyperSendmail v2004.12) id <0KHR00D00SGQ2V00@i_mtaout2.012.net.il> for gdb-patches@sources.redhat.com; Wed, 08 Apr 2009 09:55:22 +0300 (IDT)
Received: from HOME-C4E4A596F7 ([84.228.240.236]) by i_mtaout2.012.net.il (HyperSendmail v2004.12) with ESMTPA id <0KHR00HXSSK9XQD0@i_mtaout2.012.net.il>; Wed, 08 Apr 2009 09:55:22 +0300 (IDT)
Date: Wed, 08 Apr 2009 06:55:00 -0000
From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: Implement -exec-jump
In-reply-to: <200904080950.16691.vladimir@codesourcery.com>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sources.redhat.com
Reply-to: Eli Zaretskii <eliz@gnu.org>
Message-id: <838wmb63h9.fsf@gnu.org>
References: <200904080950.16691.vladimir@codesourcery.com>
X-IsSubscribed: yes
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-patches.sourceware.org>
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
X-SW-Source: 2009-04/txt/msg00139.txt.bz2

> From: Vladimir Prus <vladimir@codesourcery.com>
> Date: Wed, 8 Apr 2009 09:50:16 +0400
> 
> 
> This patch, committed, implements the -exec-jump MI command.
> (Documentation follows later)

Please don't commit patches without the docs to go with them.  Many
people (and even distributions) use development snapshots or the CVS
directly these days, and I would like to avoid the situation where
they get features without documentation.  I think we all should want
this.

It is okay to _post_ a patch for review saying that the documentation
patch will be _posted_ later, but actually _committing_ the code part
is something very different.

Thanks.