From: Vladimir Prus <ghost@cs.msu.su>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Fix crash in -var-delete
Date: Thu, 08 Nov 2007 08:39:00 -0000 [thread overview]
Message-ID: <200711081133.57745.ghost@cs.msu.su> (raw)
In-Reply-To: <20071107205502.GG3911@adacore.com>
On Wednesday 07 November 2007 23:55:02 Joel Brobecker wrote:
> > > On Wed, Nov 07, 2007 at 10:57:59PM +0300, Vladimir Prus wrote:
> > >> The patch and a testcase are attached. OK?
> > >
> > > OK (if you write the changelog)
> >
> > Thanks. Here's what I've checked in (with changelog).
>
> Can you also please commit to the branch?
Done.
> I suggest that we add a NEWS entry as well for every fixes that we make
> on the branch, that really helps my work when writing the announcement
> of a new release.
Can you clarify if you want a NEWS entry to be checked in on trunk, on
branch, or both?
- Volodya
next prev parent reply other threads:[~2007-11-08 8:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 19:58 Vladimir Prus
2007-11-07 20:00 ` Daniel Jacobowitz
2007-11-07 20:07 ` Vladimir Prus
2007-11-07 20:55 ` Joel Brobecker
2007-11-08 8:39 ` Vladimir Prus [this message]
2007-11-08 19:19 ` Joel Brobecker
2007-11-08 5:27 ` Nick Roberts
2007-11-08 7:08 ` Vladimir Prus
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=200711081133.57745.ghost@cs.msu.su \
--to=ghost@cs.msu.su \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sources.redhat.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