This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
| Other format: | [Raw text] | |
On 3/27/19 10:36 AM, Zack Weinberg wrote:
On Wed, Mar 27, 2019 at 10:33 AM Carlos O'Donell <codonell@redhat.com> wrote:Yes it is OK to push *other* patches that correct the dates to match the git commit dates.For the record, I would have assumed that correcting the date in a ChangeLog entry to match the git commit date was like correcting a typo in a comment: no approval required, just post the patch and then go ahead and commit it.
I agree. I've added it to Consensus. https://sourceware.org/glibc/wiki/Consensus#Trivial_Bug-Fix_Changes ~~~ * Anyone can commit a change to master fixing the date in a ChangeLog entry to match the git commit date. There is no need to post the patch for review, simply make the change and then push the commit. This is only allowed for master where consensus is that dates should be correct. There is still no clear consensus around what the ChangeLog date should be for a cherry-picked change into a non-master branch. ~~~ -- Cheers, Carlos.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |