Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@gnu.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: mec.gnu@mindspring.com, brobecker@gnat.com, hilfingr@gnat.com,
	gdb-patches@sources.redhat.com
Subject: Re: [PATCH]: Updates to Ada sources, part 1 (longish)
Date: Sat, 05 Jun 2004 16:07:00 -0000	[thread overview]
Message-ID: <2427-Sat05Jun2004190137+0300-eliz@gnu.org> (raw)
In-Reply-To: <40C1CB8E.7080108@gnu.org> (message from Andrew Cagney on Sat, 05 Jun 2004 09:33:02 -0400)

> Date: Sat, 05 Jun 2004 09:33:02 -0400
> From: Andrew Cagney <cagney@gnu.org>
> 
> We've on a number of occasions seen large through to extreemly large 
> merges (HP comes to mind) and on each occason the contributor, 
> unprompted, ensure that a correct ChangeLog was included.

I would even be happy if the contributor would do that when prompted
(I prompted them to begin with, remember?).

However, I'm not sure we should insist on this given the contributor's
reluctance to do that, when prompted.  It is IMHO enough to have the
required information readily available in the distribution; a separate
file will achieve just that.

> We're talking an hour or perhaphs two

How is this consistent with the fact that tree-SSA merge required a
full day of work to prepare the log entries?

> The way to do this is to ignore the history and just look at the final 
> diff.

That will lose information.

> A bit of sed'n'sort will in a matter of minutes give the functions
> added/deleted bit, leaving just terse verbage of the other functions
> changed.

If it's too terse, it isn't worth the effort.  What we need is a
description of the changes as if they were done yesterday, not an
opaque list of new, deleted, and changed functions.


  reply	other threads:[~2004-06-05 16:07 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
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 [this message]
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=2427-Sat05Jun2004190137+0300-eliz@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@gnat.com \
    --cc=cagney@gnu.org \
    --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