[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#26274: 26.0.50; completion regression
From: |
Stephen Berman |
Subject: |
bug#26274: 26.0.50; completion regression |
Date: |
Wed, 29 Mar 2017 20:43:59 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux) |
On Wed, 29 Mar 2017 21:33:57 +0300 Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Stephen Berman <stephen.berman@gmx.net>
>> Cc: 26274@debbugs.gnu.org, Noam Postavsky <npostavs@users.sourceforge.net>
>> Date: Wed, 29 Mar 2017 20:27:57 +0200
>>
>> My guess is the first of these, since it's between the bad and good
>> builds; the other two commits are much earlier. But given the above
>> make failure, I don't know how to build that commit (or the one before
>> it).
>
> You could clone the repository anew, checkout that commit, and then
> build.
On my hardware this is unfortunately very time-consuming. Is there no
other way?
Steve Berman
- bug#26274: 26.0.50; completion regression, Stephen Berman, 2017/03/27
- bug#26274: 26.0.50; completion regression, Stephen Berman, 2017/03/27
- bug#26274: 26.0.50; completion regression, Stephen Berman, 2017/03/29
- bug#26274: 26.0.50; completion regression, Noam Postavsky, 2017/03/29
- bug#26274: 26.0.50; completion regression, Stephen Berman, 2017/03/29
- bug#26274: 26.0.50; completion regression, Eli Zaretskii, 2017/03/29
- bug#26274: 26.0.50; completion regression, Michal Nazarewicz, 2017/03/30
- bug#26274: 26.0.50; completion regression, Michal Nazarewicz, 2017/03/30
- bug#26274: 26.0.50; completion regression, Michal Nazarewicz, 2017/03/30
- bug#26274: 26.0.50; completion regression, Michal Nazarewicz, 2017/03/30
- bug#26274: 26.0.50; completion regression, Stephen Berman, 2017/03/30
- bug#26274: 26.0.50; completion regression, Michal Nazarewicz, 2017/03/30
- bug#26274: 26.0.50; completion regression, Stephen Berman, 2017/03/30