STYLE: avoid spurious messages when cloning cases (0067c9e3) · Commits · Development / openfoam · GitLab

Snippets Groups Projects

GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens, and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption in our documentation.

Commit 0067c9e3 authored 8 years ago by

Mark Olesen

STYLE: avoid spurious messages when cloning cases

- either (or both) of 0/, 0.orig/ may exist, so error messages about
  one of them being missing is a bit misleading

parent ff2a3353

Branches

Tags

No related merge requests found

Hide whitespace changes

Inline Side-by-side

Showing with 18 additions and 5 deletions

Please register or to comment