Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: kettenis@science.uva.nl
Cc: drow@mvista.com, gdb-patches@sources.redhat.com
Subject: Re: What is on the 5.1 branch; Was: [rfc] Re: read_register_bytes() bug; was my Regcache revamp
Date: Mon, 20 Aug 2001 23:43:00 -0000	[thread overview]
Message-ID: <2110-Tue21Aug2001094234+0300-eliz@is.elta.co.il> (raw)
In-Reply-To: <s3ibslal73d.fsf@soliton.wins.uva.nl>

> From: Mark Kettenis <kettenis@science.uva.nl>
> Date: 21 Aug 2001 00:06:14 +0200
> > 
> > I think this is wrong: the logs should reflect the commit time, and if
> > they aren't chronologically increasing, it's hard to find a specific
> > entry and even harder to figure out which change came after which,
> > without resorting to CVS.
> 
> Oh dear!  It's the ChangeLog dating issue again.

Sorry to raise that again, but I don't think I ever saw this being
discussed since the time I became involved with GDB.  If this has been
beaten to death, it should probably be spelled out in the coding
conventions docs.  Did I miss it?

> It is generally
> accepted among the GNU projects to date the entries with the day the
> patch was last modified.

Which GNU projects are those?  Emacs is not one of them: they take
great care there to have all the entries labeled by the commit date.

> Which patch came after which is implied by
> the order in which the entries appear in the ChangeLog file.

That order can be messed up by snafus such as CVS conflicts etc.

Why is it such a problem to label the entries with the date when the
change is committed?  I don't see any disadvantages to this, only
advantages.


  reply	other threads:[~2001-08-20 23:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-18 11:08 Andrew Cagney
2001-08-18 14:04 ` [rfc] " Andrew Cagney
     [not found]   ` <9743-Sun19Aug2001093055+0300-eliz@is.elta.co.il>
2001-08-21  6:53     ` What is on the 5.1 branch; Was: " Andrew Cagney
2001-08-19 23:10       ` Eli Zaretskii
2001-08-19 23:16         ` Daniel Jacobowitz
2001-08-20  2:09           ` Eli Zaretskii
2001-08-20 15:07             ` Mark Kettenis
2001-08-20 23:43               ` Eli Zaretskii [this message]
2001-08-21  8:17                 ` Andrew Cagney
2001-08-21  9:23                   ` Eli Zaretskii
2001-08-21  6:52             ` Andrew Cagney
2001-08-21  6:52           ` Kevin Buettner
2001-08-21  6:53         ` 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=2110-Tue21Aug2001094234+0300-eliz@is.elta.co.il \
    --to=eliz@is.elta.co.il \
    --cc=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kettenis@science.uva.nl \
    /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