On 11/9/22 18:07, Alexandre Belloni wrote:
> Hi,
>
> On 01/11/2022 13:54:18-0400, Sean Anderson wrote:
>> > That would result in a lot of messages on the mailing list and ends up
>> > being a lot of work for the maintainers as well.
>>
>> If you use a tool like b4 [1] it can automatically generat
Hi,
On 01/11/2022 13:54:18-0400, Sean Anderson wrote:
> > That would result in a lot of messages on the mailing list and ends up
> > being a lot of work for the maintainers as well.
>
> If you use a tool like b4 [1] it can automatically generate a summary
> thank-you message.
> As an example, [2
> On 1 Nov 2022, at 17:40, Sean Anderson via lists.openembedded.org
> wrote:
>
> I really wish you guys sent thank-you messages when you merged something.
> Makes
> it a lot easier to keep track of which series still need work.
My workflow is to have everything I submit in a local feature bra
On Tue, 1 Nov 2022 at 19:30, Sean Anderson wrote:
> I believe in order to set up pwbot you need a computer with
>
> - The git repository you want to track on it. The easiest way to do this is
> probably to run it on git.openembedded.org itself.
> - A patchwork API key (to modify the patch status
On 11/1/22 14:02, Alexander Kanavin wrote:
> [You don't often get email from alex.kana...@gmail.com. Learn why this is
> important at https://aka.ms/LearnAboutSenderIdentification ]
>
> On Tue, 1 Nov 2022 at 18:54, Sean Anderson via lists.openembedded.org
> wrote:
>> If you use a tool like b4 [1
On Tue, 1 Nov 2022 at 19:02, Alexander Kanavin via
lists.openembedded.org
wrote:
> > You can set up something like pwbot [3], which integrates with patchwork
> > and your repository. It produces messages like [4] automatically when it
> > notices they have been merged into the repositiry, and mark
On Tue, 1 Nov 2022 at 18:54, Sean Anderson via lists.openembedded.org
wrote:
> If you use a tool like b4 [1] it can automatically generate a summary
> thank-you message.
> As an example, [2]. This keeps the number of messages down and is not terribly
> burdensome for maintainers (since it fits in
On 11/1/22 13:44, Richard Purdie wrote:
> On Tue, 2022-11-01 at 13:40 -0400, Sean Anderson wrote:
>> On 11/1/22 13:29, Richard Purdie wrote:
>> > On Tue, 2022-11-01 at 12:14 -0400, Sean Anderson wrote:
>> > > On 10/28/22 11:37, Richard Purdie wrote:
>> > > > On Fri, 2022-10-28 at 11:29 -0400, Sean
On Tue, 2022-11-01 at 13:40 -0400, Sean Anderson wrote:
> On 11/1/22 13:29, Richard Purdie wrote:
> > On Tue, 2022-11-01 at 12:14 -0400, Sean Anderson wrote:
> > > On 10/28/22 11:37, Richard Purdie wrote:
> > > > On Fri, 2022-10-28 at 11:29 -0400, Sean Anderson wrote:
> > > > > On 10/28/22 11:09, R
On 11/1/22 13:29, Richard Purdie wrote:
> On Tue, 2022-11-01 at 12:14 -0400, Sean Anderson wrote:
>> On 10/28/22 11:37, Richard Purdie wrote:
>> > On Fri, 2022-10-28 at 11:29 -0400, Sean Anderson wrote:
>> > > On 10/28/22 11:09, Richard Purdie wrote:
>> > > > On Wed, 2022-10-26 at 13:21 -0400, Sean
On Tue, 2022-11-01 at 12:14 -0400, Sean Anderson wrote:
> On 10/28/22 11:37, Richard Purdie wrote:
> > On Fri, 2022-10-28 at 11:29 -0400, Sean Anderson wrote:
> > > On 10/28/22 11:09, Richard Purdie wrote:
> > > > On Wed, 2022-10-26 at 13:21 -0400, Sean Anderson wrote:
> > > > > As noted in the cov
On 10/28/22 11:37, Richard Purdie wrote:
> On Fri, 2022-10-28 at 11:29 -0400, Sean Anderson wrote:
>> On 10/28/22 11:09, Richard Purdie wrote:
>> > On Wed, 2022-10-26 at 13:21 -0400, Sean Anderson wrote:
>> > > As noted in the cover letter, I ran
>> > >
>> > > oe-selftest -r fitimage.FitImageTests
On Fri, 2022-10-28 at 11:29 -0400, Sean Anderson wrote:
> On 10/28/22 11:09, Richard Purdie wrote:
> > On Wed, 2022-10-26 at 13:21 -0400, Sean Anderson wrote:
> > > As noted in the cover letter, I ran
> > >
> > > oe-selftest -r fitimage.FitImageTests
> >
> > Ok, good. That at least means you were
On 10/28/22 11:09, Richard Purdie wrote:
On Wed, 2022-10-26 at 13:21 -0400, Sean Anderson wrote:
On 10/26/22 13:00, Richard Purdie wrote:
On Wed, 2022-10-26 at 12:49 -0400, Sean Anderson wrote:
On 10/26/22 10:08, Richard Purdie wrote:
This looks like a pretty nice improvement, I've been worri
On Wed, 2022-10-26 at 13:21 -0400, Sean Anderson wrote:
> On 10/26/22 13:00, Richard Purdie wrote:
> > On Wed, 2022-10-26 at 12:49 -0400, Sean Anderson wrote:
> > > On 10/26/22 10:08, Richard Purdie wrote:
> > > > This looks like a pretty nice improvement, I've been worried about how
> > > > entang
On 10/26/22 13:00, Richard Purdie wrote:
> On Wed, 2022-10-26 at 12:49 -0400, Sean Anderson wrote:
>> On 10/26/22 10:08, Richard Purdie wrote:
>> > This looks like a pretty nice improvement, I've been worried about how
>> > entangled all this was becoming. Is there anything better we could do
>> >
On Wed, 2022-10-26 at 12:49 -0400, Sean Anderson wrote:
> On 10/26/22 10:08, Richard Purdie wrote:
> > This looks like a pretty nice improvement, I've been worried about how
> > entangled all this was becoming. Is there anything better we could do
> > with testing of this code? We rely increasingly
On 10/26/22 10:08, Richard Purdie wrote:
> On Fri, 2022-10-21 at 19:37 -0400, Sean Anderson wrote:
>> The U-Boot signing code is a bit of a mess. The problem is that mkimage
>> determines the public keys to embed into a device tree based on an image
>> that it is signing. This results in all sorts
The U-Boot signing code is a bit of a mess. The problem is that mkimage
determines the public keys to embed into a device tree based on an image
that it is signing. This results in all sorts of contortions: U-Boot has to
be available to the kernel recipe so that it can have the correct public
keys
19 matches
Mail list logo
