Skip to content

umpf: keep the first commit-ish for a branch when creating the umpf from an umerge#57

Merged
michaelolbrich merged 1 commit into
pengutronix:masterfrom
michaelolbrich:umerge
Jun 6, 2025
Merged

umpf: keep the first commit-ish for a branch when creating the umpf from an umerge#57
michaelolbrich merged 1 commit into
pengutronix:masterfrom
michaelolbrich:umerge

Conversation

@michaelolbrich
Copy link
Copy Markdown
Member

When an umpf is created from a umerge, the same topic branch may be found multiple times:

  1. The actual merge for the topic in the umerge
  2. as a base for another topic

The commit-ish from the first case is the relevant one. All others may use older versions of the topic branch, so ignore those when creating the useries.

Without this, creating an identical tag from a umerge will use the wrong version of the topic branch.

…rom an umerge

When an umpf is created from a umerge, the same topic branch may be
found multiple times:
1. The actual merge for the topic in the umerge
2. as a base for another topic

The commit-ish from the first case is the relevant one. All others may
use older versions of the topic branch, so ignore those when creating
the useries.

Without this, creating an identical tag from a umerge will use the wrong
version of the topic branch.

Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
@michaelolbrich michaelolbrich requested a review from a3f June 6, 2025 11:06
@a3f
Copy link
Copy Markdown
Member

a3f commented Jun 6, 2025

I am wondering if we shouldn't have a strict mode that would verify that we don't have conflicting hashes for the same topic, This fix works for me though, so:

Tested-by: Ahmad Fatoum <a.fatoum@pengutronix.de>

@michaelolbrich
Copy link
Copy Markdown
Member Author

If the hashes conflict, then umpf build should have failed already.

@michaelolbrich michaelolbrich merged commit 2679a10 into pengutronix:master Jun 6, 2025
2 checks passed
@a3f
Copy link
Copy Markdown
Member

a3f commented Jun 6, 2025

I meant the situation of having a stale umpf merge while the topic branch is newer. Do you not think it's worth nudging users to fix this?

@michaelolbrich
Copy link
Copy Markdown
Member Author

It's explicitly supported by umpf that you can use an older version as base. That avoids unnecessary rebasing.

@a3f
Copy link
Copy Markdown
Member

a3f commented Jun 6, 2025

Fair enough. Maybe a potential --strict should rather support failing the umpf tag on conflicts instead.

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.

2 participants