From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] new command: maintenance print target-stack
Date: Wed, 24 Jan 2007 19:50:00 -0000 [thread overview]
Message-ID: <uejpkcihl.fsf@gnu.org> (raw)
In-Reply-To: <20070124162036.GC4676@adacore.com> (message from Joel Brobecker on Wed, 24 Jan 2007 11:20:36 -0500)
> 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
next prev parent reply other threads:[~2007-01-24 19:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-24 1:13 Joel Brobecker
2007-01-24 4:19 ` Eli Zaretskii
2007-01-24 16:19 ` Joel Brobecker
2007-01-24 19:50 ` Eli Zaretskii [this message]
2007-01-24 20:03 ` Joel Brobecker
2007-01-24 20:05 ` Daniel Jacobowitz
2007-01-25 23:58 ` Joel Brobecker
2007-01-26 9:36 ` Eli Zaretskii
2007-01-26 22:04 ` Joel Brobecker
2007-01-27 10:33 ` Eli Zaretskii
2007-01-29 16:38 ` Joel Brobecker
2007-01-29 16:38 ` Joel Brobecker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=uejpkcihl.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox