public inbox for libc-stable@sourceware.org
 help / color / mirror / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Rafal Luzynski <digitalfreak@lingonborough.com>,
	Aurelien Jarno <aurelien@aurel32.net>,
	libc-stable@sourceware.org
Subject: Re: [2.29 COMMITTED] regex: fix read overrun [BZ #24114]
Date: Tue, 01 Jan 2019 00:00:00 -0000	[thread overview]
Message-ID: <2f242ef0-e5b9-e253-3fc2-e4886f5f9df4@cs.ucla.edu> (raw)
In-Reply-To: <1004103621.41197.1552951132012@poczta.nazwa.pl>

On 3/18/19 4:18 PM, Rafal Luzynski wrote:
> As far as I know the date in the ChangeLog should be the date
> when the change was pushed to the git repository, not when the
> patch was authored.  In case of the stable branches it should be
> the date when it was pushed to the stable branch, not when it was
> pushed to master.  Shall we change this?

I prefer ChangeLog dates to be in temporal order, so I like the rule
you're suggesting. Although Git works wonders with branching time, it
can still be a pain to spelunk when the timestamps aren't linear.

If/when we start generating ChangeLogs automatically, I hope the dates
will continue to be in temporal order.

  reply	other threads:[~2019-03-19  2:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-01  0:00 Aurelien Jarno
2019-01-01  0:00 ` [2.29 COMMITTED] Record CVE-2019-9169 in NEWS and ChangeLog " Aurelien Jarno
2019-01-01  0:00 ` [2.29 COMMITTED] regex: fix read overrun " Rafal Luzynski
2019-01-01  0:00   ` Paul Eggert [this message]
2019-01-01  0:00   ` Aurelien Jarno
2019-01-01  0:00     ` Rafal Luzynski
2019-01-01  0:00   ` Florian Weimer
2019-01-01  0:00     ` Rafal Luzynski
2019-01-01  0:00       ` Florian Weimer

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=2f242ef0-e5b9-e253-3fc2-e4886f5f9df4@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=aurelien@aurel32.net \
    --cc=digitalfreak@lingonborough.com \
    --cc=libc-stable@sourceware.org \
    /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).