Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

patches: add the required Upstream-Status to this layer patches #123

Merged
merged 1 commit into from
Nov 21, 2024

Conversation

EdTheBearded
Copy link
Contributor

Since now it is required for patches to have 'Upstream-Status', I've added 'Upstream-Status: Inappropriate [embedded specific]' to those patches, since they've been created for a long time and doesn't seem to have been upstreamed.

Since now it is required for patches to have 'Upstream-Status', I've
added 'Upstream-Status: Inappropriate [embedded specific]' to those
patches, since they've been created for a long time and doesn't seem to
have been upstreamed.

Signed-off-by: Eduardo Ferreira <eduardo.barbosa@toradex.com>
Copy link
Contributor

@quaresmajose quaresmajose left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@@ -4,6 +4,8 @@ Date: Sat, 3 Jul 2021 20:37:08 -0300
Subject: [PATCH] ostree-fetcher-curl: set a timeout for an overall request
processing

Upstream-Status: Inappropriate [embedded specific]

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I will propose a drop of this one in #119 but not yet

Copy link
Collaborator

@ricardosalveti ricardosalveti left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks!

@ricardosalveti ricardosalveti merged commit 2dd0ae4 into uptane:master Nov 21, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants