Re: [PATCH 1/3] MI: fix the result of -break-insert with multiple locations

[Mircea Gherzan <mircea.gherzan@intel.com>]

On 08.03.2013 01:15, André Pönitz wrote:
> On Thu, Mar 07, 2013 at 09:43:41PM +0000, Marc Khouzam wrote:
>>> How does the non-affectedness of a specific frontend matter
>>> in that context? Are there first and second class citizens
>>> when it comes to gdb frontends?
>>
>> I think it may simply be that Mircea is not familiar with the frontend
>> landscape.  Eclipse is not the only frontend that uses MI to control
>> GDB.  Andre takes care of another such frontend (I apologize but
>> its names escapes me right at this moment).
>
> Nevermind. Happens to me, too...
>
>> Normally, MI changes should be backwards compatible (even
>> if they are fixing something broken).  I have seen that for difficult
>> changes, exceptions were made as long as no one mentioned
>> the change broke a frontend.  This is not the case here.
>
> I have changed my side to transparently parse either result now.

Thanks!

> Nevertheless, it would be nice if the application of the patch could be
> delayed by a couple of weeks to keep the time window small where people
> might use a newer gdb with an older version of said frontend.
> That'd not exactly be vital, just - nice.

The patch as RFC was posted in January. The current version is ten days 
old. Eclipse doesn't care, your fronted can now parse this and I have 
not seen any comments from other frontend maintainers. Given this, would 
it OK to apply this _today_? Tommorow the 7.6 branch will be cut off.

Thanks,
Mircea


-- 

Intel GmbH
Dornacher Strasse 1
85622 Feldkirchen/Muenchen, Deutschland
Sitz der Gesellschaft: Feldkirchen bei Muenchen
Geschaeftsfuehrer: Christian Lamprechter, Hannes Schwaderer, Douglas Lusk
Registergericht: Muenchen HRB 47456
Ust.-IdNr./VAT Registration No.: DE129385895
Citibank Frankfurt a.M. (BLZ 502 109 00) 600119052