Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Livius" <egyszeregy@freemail.hu>
To: openembedded-core@lists.openembedded.org
Subject: Re: Patchtest results for [PATCH] archiver.bbclass: Fix work-shared checking for kernel recipes
Date: Thu, 06 Jun 2024 14:38:03 -0700	[thread overview]
Message-ID: <8404.1717709883800685810@lists.openembedded.org> (raw)
In-Reply-To: <0101018fef5da2bb-20fddbbf-ef4e-4418-90d6-c2ec76ea132b-000000@us-west-2.amazonses.com>

When i apply my patch in my git bash console i have no any error about "malformed diff lines".

Livius@DESKTOP-LIVIUS MINGW64 /d/Bosch/openembedded-core (master)
$ git am 0001-archiver.bbclass-Fix-work-shared-checking-for-kernel.patch
Applying: archiver.bbclass: Fix work-shared checking for kernel recipes

Livius@DESKTOP-LIVIUS MINGW64 /d/Bosch/openembedded-core (master)
$


WARNING: multiple messages have this Message-ID (diff)
From: "Livius" <egyszeregy@freemail.hu>
To: openembedded-core@lists.openembedded.org
Subject: Re: Patchtest results for [PATCH] archiver.bbclass: Fix work-shared checking for kernel recipes
Date: Thu, 06 Jun 2024 14:41:28 -0700	[thread overview]
Message-ID: <8404.1717709883800685810@lists.openembedded.org> (raw)
Message-ID: <20240606214128.XeATRlnbvyunRdN3LfhuMAoAxFonIQt8LgFOH_mIYJ8@z> (raw)
In-Reply-To: <0101018fef5da2bb-20fddbbf-ef4e-4418-90d6-c2ec76ea132b-000000@us-west-2.amazonses.com>

When i apply and check my patch in my git bash console i have no any error about "malformed diff lines".

Livius@DESKTOP-LIVIUS MINGW64 /d/Bosch/openembedded-core (master)
$ git apply --check 0001-archiver.bbclass-Fix-work-shared-checking-for-kernel.patch

Livius@DESKTOP-LIVIUS MINGW64 /d/Bosch/openembedded-core (master)
$ git am 0001-archiver.bbclass-Fix-work-shared-checking-for-kernel.patch
Applying: archiver.bbclass: Fix work-shared checking for kernel recipes


WARNING: multiple messages have this Message-ID (diff)
From: "Livius" <egyszeregy@freemail.hu>
To: openembedded-core@lists.openembedded.org
Subject: Re: Patchtest results for [PATCH] archiver.bbclass: Fix work-shared checking for kernel recipes
Date: Fri, 07 Jun 2024 01:26:30 -0700	[thread overview]
Message-ID: <8404.1717709883800685810@lists.openembedded.org> (raw)
Message-ID: <20240607082630.4j0KIRmYrFUrtTOuZNSjQzNQIR8u7ndqOm3UUzaKr5g@z> (raw)
In-Reply-To: <0101018fef5da2bb-20fddbbf-ef4e-4418-90d6-c2ec76ea132b-000000@us-west-2.amazonses.com>

When i apply and check my patch in my git bash console i have no any error about "malformed diff lines".

Livius@DESKTOP-LIVIUS MINGW64 /d/Yocto/openembedded-core (master)
$ git apply --check 0001-archiver.bbclass-Fix-work-shared-checking-for-kernel.patch

Livius@DESKTOP-LIVIUS MINGW64 /d/Yocto/openembedded-core (master)
$ git am 0001-archiver.bbclass-Fix-work-shared-checking-for-kernel.patch
Applying: archiver.bbclass: Fix work-shared checking for kernel recipes


  reply	other threads:[~2024-06-06 21:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-06 20:48 [PATCH] archiver.bbclass: Fix work-shared checking for kernel recipes egyszeregy
2024-06-06 21:04 ` Patchtest results for " patchtest
2024-06-06 21:38   ` Livius [this message]
2024-06-06 21:41     ` Livius
     [not found]     ` <Groupsio.1.8404.1717709883800685810@lists.openembedded.org>
2024-06-07  1:32       ` [OE-core] " Trevor Gamblin
2024-06-07  8:26     ` Livius
2024-06-11 10:48 ` [OE-core] " Ross Burton
2024-06-11 23:30   ` Livius
2024-06-11 23:31     ` Livius
2024-06-11 23:33     ` Livius
2024-06-11 23:35     ` Livius
     [not found]     ` <Groupsio.3.23837.1718148644454631767@lists.openembedded.org>
2024-06-12  9:31       ` [OE-core] " Jose Quaresma
2024-06-13 13:54         ` Livius
     [not found]       ` <17D837E52ADBFC1B.19992@lists.openembedded.org>
2024-06-13 12:21         ` [OE-core] " Jose Quaresma

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=8404.1717709883800685810@lists.openembedded.org \
    --to=egyszeregy@freemail.hu \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox