This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [patch rfa:doco rfc:NEWS] mi1 -> mi2; rm mi0



However, should the HEAD hold off on recognizing -i=mi2 until the next 
branch is cut?  On the HEAD, -i=mi evolves by definition.  However, 
-i=mi2 is evolving as well :-(



That'd be best I think.  I think that -i=mi2 specifies a fixed standard
and we don't have one yet; so how about -i=mi being different from
-i=mi1, but not adding -i=mi2 until we're ready to fix the interface?




I just looked, and I take the idea back.  It means updating NEWS, DOC 
and testsuite twice - just after the branch (to start the new interface) 
and just before a branch (to freeze the new interface).



I think its going to be easier to get it all done once just after the 
branch.  If someone reports a bug against a YYYYMMDD version of GDB then 
it's pretty clear that they are not using a released GDB.



Andrew




















  
Index Nav:
      
        [Date Index] [Subject Index] [Author Index] [Thread Index]
      
  

  
Message Nav:
      [Date Prev] [Date Next]
      [Thread Prev] [Thread Next]