From: "Rebecca Cran" <rebecca@bsdio.com>
To: "Kinney, Michael D" <michael.d.kinney@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
"sami.mujawar@arm.com" <sami.mujawar@arm.com>, nd <nd@arm.com>,
"Chen, Christine" <yuwei.chen@intel.com>
Subject: Re: [edk2-devel] [PATCH] Basetools: Include PCD declarations from Library Instance
Date: Sun, 4 Feb 2024 05:42:56 -0700 [thread overview]
Message-ID: <d8ae348a-d7c1-4c06-a54c-94ff77442dfb@bsdio.com> (raw)
In-Reply-To: <CO1PR11MB49295A95D88230BB0B8F754FD2792@CO1PR11MB4929.namprd11.prod.outlook.com>
On 1/26/24 12:49, Kinney, Michael D wrote:
> Please make sure this change is also applied to the edk2-basetools repo.
>
I'm running into a problem applying this change to edk2-basetools
because the paths and line endings are both different between the two
repos, so both "git apply" and "patch" fail.
Is there a process for converting patches between repos? It looks like
edk2-basetools is missing several commits.
--
Rebecca Cran
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#115085): https://edk2.groups.io/g/devel/message/115085
Mute This Topic: https://groups.io/mt/101922917/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2024-02-04 12:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 17:11 [edk2-devel] [PATCH] Basetools: Include PCD declarations from Library Instance levi.yun
2023-10-13 7:37 ` Sami Mujawar
2023-10-23 8:00 ` Sami Mujawar
2023-10-17 8:46 ` PierreGondois
2023-10-25 18:53 ` Rebecca Cran
2024-01-26 9:35 ` Sami Mujawar
2024-01-26 10:12 ` Sami Mujawar
2024-01-26 19:49 ` Michael D Kinney
2024-02-04 12:42 ` Rebecca Cran [this message]
2024-02-08 23:54 ` Rebecca Cran
2024-01-30 21:07 ` Rebecca Cran
2024-01-26 10:06 ` Sami Mujawar
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-list 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=d8ae348a-d7c1-4c06-a54c-94ff77442dfb@bsdio.com \
--to=devel@edk2.groups.io \
/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