From: Tom Tromey <tromey@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Vladimir Prus <vladimir@codesourcery.com>,
gdb-patches@sources.redhat.com
Subject: Re: Implement -exec-jump
Date: Wed, 08 Apr 2009 16:26:00 -0000 [thread overview]
Message-ID: <m3myarxgbk.fsf@fleche.redhat.com> (raw)
In-Reply-To: <8363hf5xsc.fsf@gnu.org> (Eli Zaretskii's message of "Wed\, 08 Apr 2009 11\:56\:19 +0300")
>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
Vladimir> I though there's "in a published release" somewhere in the
Vladimir> above statement.
Eli> That's exactly the point: the release of GDB 7.0 is quite close.
Eli> Since we don't have any means to track such issues, you are now
Eli> effectively asking me to somehow make sure the appropriate
Eli> documentation patch is committed before the release, preferably before
Eli> the branch.
If we want, we can use Bugzilla to track release blockers.
There are a few options for the mechanics of this.
In this particular case, I'd imagine that the documentation patch is
not much longer than the Bugzilla entry though :-)
Tom
next prev parent reply other threads:[~2009-04-08 16:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 5:50 Vladimir Prus
2009-04-08 6:55 ` Eli Zaretskii
2009-04-08 7:08 ` Vladimir Prus
2009-04-08 7:22 ` Eli Zaretskii
2009-04-08 7:36 ` Vladimir Prus
2009-04-08 9:00 ` Eli Zaretskii
2009-04-08 16:26 ` Tom Tromey [this message]
2009-04-22 12:57 ` Vladimir Prus
2009-04-22 17:26 ` Eli Zaretskii
2009-04-08 9:16 ` André Pönitz
2009-04-08 9:29 ` Eli Zaretskii
2009-04-08 11:05 ` André Pönitz
2009-04-08 11:46 ` Eli Zaretskii
2009-04-08 21:51 ` Thiago Jung Bauermann
2009-04-08 21:57 ` Joel Brobecker
2009-04-10 16:50 ` Eli Zaretskii
2009-04-13 17:24 ` Tom Tromey
2009-04-08 16:28 ` Tom Tromey
2009-04-08 22:03 ` Thiago Jung Bauermann
2009-04-22 12:09 ` Vladimir Prus
2009-04-22 17:16 ` Eli Zaretskii
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=m3myarxgbk.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=vladimir@codesourcery.com \
/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