From: "Doug Smythies" <dsmythies@telus.net>
To: mmarek@suse.cz
Cc: riku.voipio@linaro.org, linux-kbuild@vger.kernel.org,
'Kalle Valo' <kvalo@codeaurora.org>,
'Ben Hutchings' <ben@decadent.org.uk>,
Doug Smythies <dsmythies@telus.net>
Subject: RE: [PATCH v2] builddeb: remove debian/files before build
Date: Sun, 4 Oct 2015 18:03:20 -0700 [thread overview]
Message-ID: <002801d0ff09$a23930f0$e6ab92d0$@net> (raw)
In-Reply-To: <87oagun1ax.fsf@kamboji.qca.qualcomm.com>
On 2015.09.22 04:25 Kalle Valo wrote:
> Ben Hutchings <ben@decadent.org.uk> writes:
>> On Tue, 2015-09-15 at 21:11 +0300, riku.voipio@linaro.org wrote:
>>> From: Riku Voipio <riku.voipio@linaro.org>
>>>
>>> As debian/files keeps accumulating entries, the changes file
>>> will end up growing indefinelty. Remove the file in clean
>>> rule and before build starts.
>>>
>>> Signed-off-by: Riku Voipio <riku.voipio@linaro.org>
>>> Reported-by: Doug Smythies <dsmythies@telus.net>
>> [...]
>>
>> FWIW:
>>
>> Acked-by: Ben Hutchings <ben@decadent.org.uk>
>
> Marek, this is a pretty annoying regression. Is it possible to get this
> to 4.3?
Perhaps I do not understand the process here, but having reported the issue
within a day of kernel 4.3-rc1 being released, and then what seems to be an
acceptable patch being suggested, and tested, with plenty of time to make
into -rc2, why hasn't it been included yet (-rc4)?
next prev parent reply other threads:[~2015-10-05 1:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-15 18:11 [PATCH v2] builddeb: remove debian/files before build riku.voipio
2015-09-15 18:21 ` Kalle Valo
2015-09-15 19:11 ` Doug Smythies
2015-09-16 6:55 ` Riku Voipio
2015-09-21 18:09 ` Ben Hutchings
2015-09-22 11:25 ` Kalle Valo
2015-10-05 1:03 ` Doug Smythies [this message]
2015-10-05 12:39 ` Riku Voipio
2015-10-05 20:49 ` Andrew Morton
2015-10-06 7:05 ` [PATCH v3] " riku.voipio
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='002801d0ff09$a23930f0$e6ab92d0$@net' \
--to=dsmythies@telus.net \
--cc=ben@decadent.org.uk \
--cc=kvalo@codeaurora.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=riku.voipio@linaro.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