This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: mi/ChangeLog et.al.
- From: Eli Zaretskii <eliz at elta dot co dot il>
- To: mec dot gnu at mindspring dot com (Michael Elizabeth Chastain)
- Cc: cagney at gnu dot org,gdb-patches at sources dot redhat dot com
- Date: 12 Jan 2004 08:01:17 +0200
- Subject: Re: mi/ChangeLog et.al.
- References: <20040111221854.158014ACDA@berman.michael-chastain.com>
- Reply-to: Eli Zaretskii <eliz at elta dot co dot il>
> Date: Sun, 11 Jan 2004 17:18:54 -0500 (EST)
> From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
>
> The intent is that there will never be a file named 'ChangeLog'
> testsuite/gdb.mi again.
We don't have any 100% fool-proof machinery to do that. Unless they
all use Emacs, someone could simply create a ChangeLog file and commit
it.
> So actually, if someone does re-create testsuite/gdb.mi/ChangeLog, then
> the ARI entry for "duplicate files" should not be solved by adding
> fnchange.lst entries, it should be solved by removing
> testsuite/gdb.mi/ChangeLog and putting the new entries in
> testsuite/ChangeLog where they belong. The ARI 8.3 warning is thus
> a twisted kind of feature. :)
Someone swift enough might check-in additional lines for fnchange.lst
without waiting for ARI's alert.
Also, if you want precedents for the names I suggested, gdb/tcl/ has
ChangeLog files with the .NNNN extension.
Anyway, there's no much sense in continuing this argument. I already
said that I'll leave it up to Andrew to decide; I'll go along with
whatever he finds best.