Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@gnu.org>
To: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
Cc: brobecker@gnat.com, gdb-patches@sources.redhat.com, hilfingr@gnat.com
Subject: Re: [PATCH]: Updates to Ada sources, part 1 (longish)
Date: Fri, 04 Jun 2004 11:45:00 -0000	[thread overview]
Message-ID: <2914-Fri04Jun2004144147+0300-eliz@gnu.org> (raw)
In-Reply-To: <20040603051228.E269F4B104@berman.michael-chastain.com> (mec.gnu@mindspring.com)

> Date: Thu,  3 Jun 2004 01:12:28 -0400 (EDT)
> From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
> 
> Speaking as a consumer of ChangeLogs, I would favor just importing
> ChangeLog.GNAT into the FSF repository, with a note at the top of
> it saying "these are changes from $date to $date done by ACT and
> merged on 2004-06-02."

That'd be fine with me, but I'd also suggest to have a pointer to
ChangeLog.GNAT in gdb/ChangeLog, right where the import of Ada changes
is recorded.  Something like "See ChangeLog.GNAT for details of the
changes."

An alternative idea is to put the contents of ChangeLog.GNAT into
gdb/ChangeLog, but indent it so that the date/time stamps of the
included ChangeLog.GNAT are not aligned with the rest of time stamps,
and thus the time monotonicity is not disrupted.  I think the Texinfo
project did that in the past when large changes were merged that were
maintained separately for some time.


  parent reply	other threads:[~2004-06-04 11:45 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-03  5:12 Michael Elizabeth Chastain
2004-06-03  7:05 ` Paul Hilfinger
2004-06-04 11:45 ` Eli Zaretskii [this message]
2004-06-04 18:32   ` Andrew Cagney
2004-06-04 18:37     ` Joel Brobecker
2004-06-04 18:55       ` Daniel Jacobowitz
2004-06-04 19:10         ` Andrew Cagney
2004-06-05 10:11     ` Eli Zaretskii
2004-06-05 13:33       ` Andrew Cagney
2004-06-05 16:07         ` Eli Zaretskii
2004-06-05 23:15           ` Paul Hilfinger
2004-06-06  4:08             ` Eli Zaretskii
2004-06-07 13:40               ` Andrew Cagney
  -- strict thread matches above, loose matches on Subject: below --
2004-06-05 14:26 Michael Elizabeth Chastain
2004-06-05 16:06 ` Eli Zaretskii
2004-06-02 10:03 Paul Hilfinger
2004-06-03  4:06 ` Eli Zaretskii
2004-06-03  4:16   ` Joel Brobecker
2004-06-03  4:30     ` Eli Zaretskii
2004-06-03  4:41       ` Joel Brobecker
2004-06-04 11:43         ` Eli Zaretskii

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=2914-Fri04Jun2004144147+0300-eliz@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@gnat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=hilfingr@gnat.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