pending/1698: Re: gdb.mi/mi2-file.exp: ChangeLog, copyright, sync with mi-file.exp

[mec dot gnu at mindspring dot com (Michael Elizabeth Chastain)]

>Number:         1698
>Category:       pending
>Synopsis:       Re: gdb.mi/mi2-file.exp: ChangeLog, copyright, sync with mi-file.exp
>Confidential:   yes
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          change-request
>Submitter-Id:   unknown
>Arrival-Date:   Mon Jun 28 20:58:01 UTC 2004
>Closed-Date:
>Last-Modified:
>Originator:     
>Release:        
>Organization:
>Environment:
>Description:
 > I am going to update the mi-file.exp to test my new functionality. I
 > am going to make mi2-file.exp the way it was before I changed it.
 > So, I should have a changelog only for mi-file.exp.
 >    mi2-file.exp will be reverted to as it was before my change.
 >    mi-file.exp will test the new command -file-list-exec-source-files.
 
 Generally we don't retroactively edit ChangeLog's, we only add
 new entries.
 
 I would do:
 
 (1) Revert the change to mi2-file.exp.  Use a normal ChangeLog
     entry for this, which says: "mi2-file.exp: Reverted undocumented
     change from 2004-NN-NN".  Send it to gdb-patches and ask
     Andrew or Elena to approve it.
 
 (2) Write a new patch for mi-file.exp, with a normal ChangeLog
     entry, and remember to hit the copyright years.
 
 In truth gdb.mi doesn't belong to me, it is in the domain of Andrew or
 Elena, so anything that Andrew or Elena say is more important than
 anything I say.  In fact you might wanna just ignore this whole message
 and just do whatever A/E say!
 
 Michael C
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: