public inbox for
 help / color / mirror / Atom feed
From: Rafal Luzynski <>
To: Florian Weimer <>
Cc: Aurelien Jarno <>,,	Paul Eggert <>
Subject: Re: [2.29 COMMITTED] regex: fix read overrun [BZ #24114]
Date: Tue, 01 Jan 2019 00:00:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

19.03.2019 17:32 Florian Weimer <> wrote:
> * Rafal Luzynski:
> > 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.
> I have been following this more or less meticulously for master, but

Thank you.

> does anyone know the rationale for it?

I guess the original reason was to know when a particular change was
actually pushed to master and thus made official.  It's not much helpful
to know when a patch was authored which may actually be the date when
the original author had started working on this (rather than finished).

I think somebody told this on libc-alpha but indeed, it was in the
context of the master branch.

> [...]
> At commit/push time (not at contribution time), the copyright
> assignment may no longer be in effect for new contributions from the
> same person, after all.

I am not a lawyer so I should not speak about it... But should the
commit/push ever happen if the copyright assignment is no longer in

Just to summarize, I am not asking for any specific rule for dates
in ChangeLog in stable branches because I can see now that nobody
needs such a rule.  Regarding the master branch, I'm not sure about
the rules but I can see that everybody (or almost everybody) update
the dates to the current date when pushing which is OK.



  reply	other threads:[~2019-03-19 22:27 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
2019-01-01  0:00   ` Florian Weimer
2019-01-01  0:00     ` Rafal Luzynski [this message]
2019-01-01  0:00       ` Florian Weimer
2019-01-01  0:00   ` Aurelien Jarno
2019-01-01  0:00     ` Rafal Luzynski

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* 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).