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

verify-commits: error and exit cleanly when git is too old. #27461

Merged
merged 1 commit into from Apr 14, 2023

Conversation

theuni
Copy link
Member

@theuni theuni commented Apr 13, 2023

Requested by fanquake. Rather than failing with a cryptic error with older git, fail gracefully and mention why.

The new option semantics are explained here.

Note: my local git versions are currently too old to test the new functionality, so I've only verified the failure case.

@DrahtBot
Copy link
Contributor

DrahtBot commented Apr 13, 2023

The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

Reviews

See the guideline for information on the review process.

Type Reviewers
ACK josibake, achow101
Concept ACK glozow

If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update.

@fanquake fanquake added this to the 25.0 milestone Apr 14, 2023
Copy link
Member

@glozow glozow left a comment

Choose a reason for hiding this comment

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

concept ACK

@josibake
Copy link
Member

ACK 1fefcf2

was able to verify the failure case (v2.34) and the happy case (v2.4)

@achow101
Copy link
Member

ACK 1fefcf2

@achow101 achow101 merged commit 69460bd into bitcoin:master Apr 14, 2023
16 checks passed
sidhujag pushed a commit to syscoin/syscoin that referenced this pull request Apr 14, 2023
…is too old.

1fefcf2 verify-commits: error and exit cleanly when git is too old. (Cory Fields)

Pull request description:

  Requested by fanquake. Rather than failing with a cryptic error with older git, fail gracefully and mention why.

  The new option semantics [are explained here](git/git@1f0c3a2).

  Note: my local git versions are currently too old to test the new functionality, so I've only verified the failure case.

ACKs for top commit:
  josibake:
    ACK bitcoin@1fefcf2
  achow101:
    ACK 1fefcf2

Tree-SHA512: f3dc583edf6ff6ff9bf06f33de967e10b8423ce62e7370912ffdca8a4ca4bfe4c2e783e9ad76281ce9e6748a4643d187aa5cb4a6b9ec4c1582910f02b94b6e3c
@bitcoin bitcoin locked and limited conversation to collaborators Apr 13, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants