From: Adrian Bunk <bunk@stusta.de>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/2] ethtool, libcap: fix upstream version check
Date: Wed, 2 Oct 2019 21:18:21 +0300 [thread overview]
Message-ID: <20191002181821.GB14877@localhost> (raw)
In-Reply-To: <CANNYZj89n07FE7UEo5DdwCs_q2xUePEh_MZgwZ=uYX1hyRqDnA@mail.gmail.com>
On Wed, Oct 02, 2019 at 08:08:08PM +0200, Alexander Kanavin wrote:
> On Wed, 2 Oct 2019 at 19:51, Adrian Bunk <bunk@stusta.de> wrote:
>
> > Works for me without your patch:
>
> I am not sure what this may mean; but for me the patch definitely solves
> the problem.
It means that even without your patch devtool is able to tell me that
there is a new upstream version of ethtool available.
I was originally wondering whether there is a problem that also affects
other users of KERNELORG_MIRROR, and was then surprised that it worked
for me without the change the way I tried.
How are you reproducing the problem?
> Alex
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2019-10-02 18:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-02 12:00 [PATCH 1/2] binutils: drop UPSTREAM_VERSION_UNKNOWN Alexander Kanavin
2019-10-02 12:00 ` [PATCH 2/2] ethtool, libcap: fix upstream version check Alexander Kanavin
2019-10-02 17:51 ` Adrian Bunk
2019-10-02 18:08 ` Alexander Kanavin
2019-10-02 18:18 ` Adrian Bunk [this message]
2019-10-02 18:27 ` Alexander Kanavin
2019-10-02 20:20 ` Adrian Bunk
2019-10-03 17:01 ` Adrian Bunk
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=20191002181821.GB14877@localhost \
--to=bunk@stusta.de \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.