From: Mark Kettenis <kettenis@science.uva.nl>
To: Eli Zaretskii <eliz@is.elta.co.il>
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 15:07:00 -0000 [thread overview]
Message-ID: <s3ibslal73d.fsf@soliton.wins.uva.nl> (raw)
In-Reply-To: <8011-Mon20Aug2001120810+0300-eliz@is.elta.co.il>
"Eli Zaretskii" <eliz@is.elta.co.il> writes:
> > Date: Sun, 19 Aug 2001 23:17:47 -0700
> > From: Daniel Jacobowitz <drow@mvista.com>
> > >
> > > Why aren't the entries there in chronological order?
> >
> > I tend to date ChangeLog entries with the day the patch was last
> > modified, not the day it was committed.
>
> 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. It is generally
accepted among the GNU projects to date the entries with the day the
patch was last modified. Which patch came after which is implied by
the order in which the entries appear in the ChangeLog file.
Mark
next prev parent reply other threads:[~2001-08-20 15:07 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 [this message]
2001-08-20 23:43 ` Eli Zaretskii
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=s3ibslal73d.fsf@soliton.wins.uva.nl \
--to=kettenis@science.uva.nl \
--cc=drow@mvista.com \
--cc=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.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