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: Tue, 06 Jan 2004 06:26:00 -0000 [thread overview]
Message-ID: <uptdxd22w.fsf@elta.co.il> (raw)
In-Reply-To: <20040105211031.C07C74B35A@berman.michael-chastain.com> (mec.gnu@mindspring.com)
> Date: Mon, 5 Jan 2004 16:10:31 -0500 (EST)
> From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
>
> How about:
>
> gdb.mi/ChangeLog-1995
> gdb.mi/ChangeLog-1996
> gdb.mi/ChangeLog-1997
> gdb.mi/ChangeLog-1998
> gdb.mi/ChangeLog-1999
> gdb.mi/ChangeLog-2000
> gdb.mi/ChangeLog-2001
> gdb.mi/ChangeLog-2002
> gdb.mi/ChangeLog-2003
> testsuite/gdb.mi/ChangeLog-1999
> testsuite/gdb.mi/ChangeLog-2000
> testsuite/gdb.mi/ChangeLog-2001
> testsuite/gdb.mi/ChangeLog-2002
> testsuite/gdb.mi/ChangeLog-2003
I don't get it: gdb/mi/ and gdb/testsuite/gdb.mi/ both have a single
ChangeLog file. Why would we want to create multiple files from them?
If all you want is to slightly change the name and put the years in
it, why not simply
gdb/mi/ChangeLog.1995-2003
gdb/testsuite/gdb.mi/ChangeLog.1999-2003
?
next prev parent reply other threads:[~2004-01-06 6:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-05 21:10 Michael Elizabeth Chastain
2004-01-06 6:26 ` Eli Zaretskii [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-11 22:19 Michael Elizabeth Chastain
2004-01-12 6:02 ` Eli Zaretskii
2004-01-12 15:28 ` Andrew Cagney
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 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=uptdxd22w.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