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

Do not use --date=iso-strict in DEAL_II_QUERY_GIT_INFORMATION #14204

Closed
wants to merge 1 commit into from

Conversation

peterrum
Copy link
Member

@tamiko I have on an old cluster problems with iso-strict, since on that system git (git version 1.8.3.1) does not know this format. The result that I get know info regarding the git version at all. Could we switch to the default format? What was the reason to selecting that format?

#

EXECUTE_PROCESS(
COMMAND ${GIT_EXECUTABLE} log -n 1 --pretty=format:"revision=%H, shortrev=%h, date=%cd" --date=iso-strict
COMMAND ${GIT_EXECUTABLE} log -n 1 --pretty=format:"revision=%H, shortrev=%h, date=%cd" --date=default
Copy link
Member

Choose a reason for hiding this comment

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

Let's not switch to default here. The reason for "iso-strict" here is to get a parseable output: 2022-08-04T13:22:13-04:00.

Default output produces probably a locale dependent string - which is a nightmare.

Would you mind testing #14206 which avoids the option for all git versions older than 2.2.

@peterrum
Copy link
Member Author

Closing in favor of #14206.

@peterrum peterrum closed this Aug 21, 2022
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.

None yet

2 participants