Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@elta.co.il>
To: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
Cc: cagney@gnu.org,gdb-patches@sources.redhat.com
Subject: Re: mi/ChangeLog et.al.
Date: Mon, 12 Jan 2004 06:02:00 -0000	[thread overview]
Message-ID: <ueku5bt8y.fsf@elta.co.il> (raw)
In-Reply-To: <20040111221854.158014ACDA@berman.michael-chastain.com> (mec.gnu@mindspring.com)

> 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.


  reply	other threads:[~2004-01-12  6:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-11 22:19 Michael Elizabeth Chastain
2004-01-12  6:02 ` Eli Zaretskii [this message]
2004-01-12 15:28   ` Andrew Cagney
  -- strict thread matches above, loose matches on Subject: below --
2004-01-11 22:10 Michael Elizabeth Chastain
2004-01-06  6:58 Michael Elizabeth Chastain
2004-01-07 16:01 ` Andrew Cagney
2004-01-11 18:35   ` Andrew Cagney
2004-01-11 18:43   ` Andrew Cagney
2004-01-11 20:57     ` Eli Zaretskii
2004-01-11 21:17       ` Andrew Cagney
2004-01-11 22:00         ` Eli Zaretskii
2004-01-05 21:10 Michael Elizabeth Chastain
2004-01-06  6:26 ` Eli Zaretskii
2004-01-05 20:22 Andrew Cagney

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=ueku5bt8y.fsf@elta.co.il \
    --to=eliz@elta.co.il \
    --cc=cagney@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mec.gnu@mindspring.com \
    /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