bpo-27593: Revise git SCM build info. (#744) (#746)#1392
Conversation
Sorry, something went wrong.
Use --short form of git hash. Use output from "git describe" for tag. Expected outputs: 1. previous hg 2. previous git 3. updated git Release (tagged) build: 1. Python 3.7.0a0 (v3.7.0a0:4def2a2901a5, ... 2. Python 3.7.0a0 (v3.7.0a0^0:05f53735c8912f8df1077e897f052571e13c3496, ... 3. Python 3.7.0a0 (v3.7.0a0:05f53735c8, ... Development build: 1. Python 3.7.0a0 (default:41df79263a11, ... 2. Python 3.7.0a0 (master:05f53735c8912f8df1077e897f052571e13c3496, ... 3. Python 3.7.0a0 (heads/master-dirty:05f53735c8, ... "dirty" means the working tree has uncommitted changes. See "git help describe" for more info. (cherry picked from commit 554626a) (cherry picked from commit ed512cb)
zooba
left a comment
zooba
left a comment
There was a problem hiding this comment.
I would be okay with simplifying the "-dirty" suffix to a single obvious character, but not a huge deal.
Sorry, something went wrong.
|
@zooba something like |
Sorry, something went wrong.
|
@zooba: "I would be okay with simplifying the "-dirty" suffix to a single obvious character, but not a huge deal." If we change something, I would also suggest to replace "heads/master" with "master". I also like replacing "master-dirty" with "master*". But this change is just a backport to make 2.7 consistent with other branches. I would suggest to first modify the master branch. |
Sorry, something went wrong.
Use --short form of git hash. Use output from "git describe" for tag.
Expected outputs:
Release (tagged) build:
Development build:
"dirty" means the working tree has uncommitted changes.
See "git help describe" for more info.
(cherry picked from commit 554626a)
(cherry picked from commit ed512cb)