From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] support/scripts/check-uniq-files: Only report each package once
Date: Tue, 8 Jan 2019 22:18:41 +0100 [thread overview]
Message-ID: <20190108211841.GH4022@scaer> (raw)
In-Reply-To: <CABhNV21ZyEzEbj0oUy59Phn63_i0PKiu-NTr+ZFLmL-mRNT7Rw@mail.gmail.com>
Einar, All,
On 2019-01-08 11:06 +0100, Einar J?n spake thusly:
> my bad. Not an issue on master.
No problem! It at least made me look at it again and came up with an
alternate solution. Thanks for the report! :-)
> On Wed, 2 Jan 2019 at 13:12, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> > On 2018-12-30 23:02 +0100, Yann E. MORIN spake thusly:
> > > On 2018-12-11 15:05 +0100, Einar Jon Gunnarsson spake thusly:
> > > > Rebuilding the same package should not trigger
> > > > a 'touched by more than one package' warning
> >
> > In fact, commit d3dca1e993 (core/pkg-generic: only save latest package
> > list) should have already fixed that case, no?
[--SNIP--]
> I was using 2018.02, but I tested this on the buildroot git repo
> before submitting.
> I must have had an older version checked out for the testing.
> I've now updated to 2018.08 and this is no longer an issue.
> Sorry about that.
No worries.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
prev parent reply other threads:[~2019-01-08 21:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 14:05 [Buildroot] [PATCH 1/1] support/scripts/check-uniq-files: Only report each package once Einar Jon Gunnarsson
2018-12-30 22:02 ` Yann E. MORIN
2019-01-02 12:12 ` Yann E. MORIN
2019-01-08 10:06 ` Einar Jón
2019-01-08 21:18 ` Yann E. MORIN [this message]
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=20190108211841.GH4022@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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.