From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-47356-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 30322 invoked by alias); 24 Jan 2007 19:50:11 -0000
Received: (qmail 30312 invoked by uid 22791); 24 Jan 2007 19:50:10 -0000
X-Spam-Check-By: sourceware.org
Received: from heller.inter.net.il (HELO heller.inter.net.il) (213.8.233.23)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 24 Jan 2007 19:50:01 +0000
Received: from HOME-C4E4A596F7 (IGLD-80-230-33-117.inter.net.il [80.230.33.117]) 	by heller.inter.net.il (MOS 3.7.3a-GA) 	with ESMTP id BRU36551 (AUTH halo1); 	Wed, 24 Jan 2007 21:49:48 +0200 (IST)
Date: Wed, 24 Jan 2007 19:50:00 -0000
Message-Id: <uejpkcihl.fsf@gnu.org>
From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
CC: gdb-patches@sourceware.org
In-reply-to: <20070124162036.GC4676@adacore.com> (message from Joel Brobecker 	on Wed, 24 Jan 2007 11:20:36 -0500)
Subject: Re: [RFA] new command: maintenance print target-stack
Reply-to: Eli Zaretskii <eliz@gnu.org>
References: <20070124011254.GG4667@adacore.com> <uodopcb12.fsf@gnu.org> <20070124162036.GC4676@adacore.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: 2007-01/txt/msg00505.txt.bz2

> Date: Wed, 24 Jan 2007 11:20:36 -0500
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: gdb-patches@sourceware.org
> 
> Did I really promise some doco as well? Must have been a moment of
> weakness... ;-)

Yes, it did sound strange ;-)

> No worries about the documentation. I promise (again!) that I will write
> something as soon as the patch is finalized and checked in (that way,
> I'm sure I document what gets checked in).

I'd really, really ask not to check in code without the docs to
accompany it.  I'd like to avoid even the slightest chance that a
snapshot gets tarred and fetched by someone between the code and the
documentation checkins.

If you want to wait with the documentation until the code is approved,
it's fine by me, but please at that time post a unified patch that
includes both the code and doco, and commit both after my approval.

TIA