[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: High CPU use on BTRFS and some other details in the stable release p
|
From: |
James Youngman |
|
Subject: |
Re: High CPU use on BTRFS and some other details in the stable release package. |
|
Date: |
Thu, 3 Nov 2016 23:10:38 +0000 |
On Wed, Nov 2, 2016 at 10:27 PM, Bernhard Voelker
<address@hidden> wrote:
> On 11/02/2016 10:55 AM, James Youngman wrote:
>> On Tue, Nov 1, 2016 at 6:04 PM, Bernhard Voelker
>> <address@hidden> wrote:
>>> On 10/03/2016 04:30 PM, Steve wrote:
>>>> The entire ChangeLog-2013 content is duplicated in ChangeLog
>>>
>>> Fixed with
>>>
>>> [PATCH 2/3] maint: remove ChangeLog-2013 from distribution tarball
>>
>> Are you sure this is the right fix? I thought that the ChangeLog we
>> generated from the git log was supposed to only go back a while
>> (perhaps only to 2013) leaving the older content in the ChageLog-2013
>> file.
>>
>> IIRC the idea behind this is that we could commit fixes to
>> ChangeLog-2013 (i.e. the historic ChangeLog entries) file directly,
>> without needing to repeatedly hack on build-aux/git-log-fix.
>
> It is exactly like that: looking at 'build-aux/gen-changelog.sh',
> you'll see that the final changelog is built from git log since 2014,
> and ChangeLog-2013 is simply concatenated.
> Thus, there's no need to ship that file in addition.
I see what you mean; I agree that this is the right fix. Thanks.
James.