From: Vladimir Prus <ghost@cs.msu.su>
To: Nick Roberts <nickrob@snap.net.nz>, gdb-patches@sources.redhat.com
Subject: Re: MI: Another -var-update bug? [PATCH]
Date: Thu, 04 Jan 2007 18:51:00 -0000 [thread overview]
Message-ID: <E1H2Xfv-0007Mc-LM@zigzag.lvk.cs.msu.su> (raw)
In-Reply-To: <17817.34669.993434.397044@kahikatea.snap.net.nz>
Nick Roberts wrote:
> > > Good, that's not bad at all. If Vlad doesn't think this is likely to
> > > break kdevelop or Eclipse, the patch is OK.
> >
> > So, given that, why did you commit it? Maybe Vlad agreed with the
> > patch in another thread that I didn't read?
>
> He was part of the original thread and had posted messages subsequent to
> yours. I presumed that if he thought it would break anything he would have
> said so.
Had I immediately knew that this patch will break something, I'd say so.
But in practice, while I'm sure KDevelop won't care, I was not able to
make definite statement about Eclipse without looking at the code, and
I had no time for such look back then.
Given that this is already checked in, I'll let you know if I find any
problems with Eclipse.
- Volodya
next prev parent reply other threads:[~2007-01-04 18:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-12 11:09 MI: Another -var-update bug? Nick Roberts
2006-12-13 6:32 ` MI: Another -var-update bug? [PATCH] Nick Roberts
2006-12-30 15:06 ` Daniel Jacobowitz
2006-12-30 22:43 ` Nick Roberts
2006-12-31 2:19 ` Daniel Jacobowitz
2007-01-01 16:24 ` Daniel Jacobowitz
2007-01-01 22:13 ` Nick Roberts
2007-01-04 18:51 ` Vladimir Prus [this message]
2007-01-04 19:43 ` Nick Roberts
2007-01-04 18:49 ` Vladimir Prus
2007-01-04 23:59 ` Nick Roberts
2007-01-05 9:10 ` Vladimir Prus
2007-01-05 15:10 ` Daniel Jacobowitz
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=E1H2Xfv-0007Mc-LM@zigzag.lvk.cs.msu.su \
--to=ghost@cs.msu.su \
--cc=gdb-patches@sources.redhat.com \
--cc=nickrob@snap.net.nz \
/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