From: Bernard Dautrevaux <Dautrevaux@microprocess.com>
To: 'Fernando Nasser' <fnasser@cygnus.com>,
insight@sources.redhat.com, Tom Tromey <tromey@cygnus.com>
Subject: RE: Unified gdbtk/ChangeLog for 2001?
Date: Fri, 15 Dec 2000 05:17:00 -0000 [thread overview]
Message-ID: <17B78BDF120BD411B70100500422FC6309E192@IIS000> (raw)
> -----Original Message-----
> From: Fernando Nasser [ mailto:fnasser@cygnus.com ]
> Sent: Thursday, December 14, 2000 3:09 PM
> To: insight@sources.redhat.com; Tom Tromey
> Subject: Unified gdbtk/ChangeLog for 2001?
>
>
> Tom has suggested that we unify the ChangeLog files that are split
> between the library and generic subdirectories.
>
> The main argument is that the current arrangement makes it
> difficult to track
> changes that affect both Tcl and C code. And the elimination
> of gdb_cmd
> and gdb_immediate will just add about 50 entries like that.
>
> The caveat is that we will have to write library/...
> generic/... in front
> of each file name.
>
> I am saving the previous years as ChangeLog-YYYY (leaving them in the
> subdirectories as they are).
>
> The question is how should we handle 2001.
> Who is in favor of a unified ChangeLog
>
> Cast your votes (they will be hand counted).
> Voting closes at 8am E.S.T. tomorrow.
>
> (I vote yes.)
>
Me too (I hope foreign absentee ballots will not be discarded :) :) :))
--------------------------------------------
Bernard Dautrevaux
Microprocess Ingenierie
97 bis, rue de Colombes
92400 COURBEVOIE
FRANCE
Tel: +33 (0) 1 47 68 80 80
Fax: +33 (0) 1 47 88 97 85
e-mail: dautrevaux@microprocess.com
b.dautrevaux@usa.net
--------------------------------------------
next reply other threads:[~2000-12-15 5:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-15 5:17 Bernard Dautrevaux [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-12-14 6:09 Fernando Nasser
2000-12-14 7:22 ` Keith Seitz
2000-12-14 7:55 ` Christopher Faylor
2000-12-14 8:52 ` Syd Polk
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=17B78BDF120BD411B70100500422FC6309E192@IIS000 \
--to=dautrevaux@microprocess.com \
--cc=fnasser@cygnus.com \
--cc=insight@sources.redhat.com \
--cc=tromey@cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).