If you are self-compiling and reporting bugs, please post the commit hash.
If you are unsure, simply type "git describe --tags" in your source tree. Or type "git rev-parse HEAD". If using a devbuild, simply open your INI and copy the first line.
Use whichever format you like best. Either way though, don't use "HEAD".
"HEAD" is not a valid commit!
Moderator: GZDoom Developers
Forum rules
Please construct and post a simple demo whenever possible for all bug reports. Please provide links to everything.
If you can include a wad demonstrating the problem, please do so. Bug reports that include fully-constructed demos have a much better chance of being investigated in a timely manner than those that don't.
Please make a new topic for every bug. Don't combine multiple bugs into a single topic. Thanks!
Please construct and post a simple demo whenever possible for all bug reports. Please provide links to everything.
If you can include a wad demonstrating the problem, please do so. Bug reports that include fully-constructed demos have a much better chance of being investigated in a timely manner than those that don't.
Please make a new topic for every bug. Don't combine multiple bugs into a single topic. Thanks!
-
Rachael
- Posts: 13718
- Joined: Tue Jan 13, 2004 1:31 pm
- Preferred Pronouns: She/Her
-
_mental_
-
- Posts: 3814
- Joined: Sun Aug 07, 2011 4:32 am
Re: "HEAD" is not a valid commit!
The same applies to "latest", "current", "March 13th", and so on. A commit time has nothing to do with a push time, they are unrelated.
Commit hashes exist for this reason, to uniquely identify the state of source code.
You want to point to a particular commit, post a hash, or better insert a GitHub link to it.
Commit hashes exist for this reason, to uniquely identify the state of source code.
You want to point to a particular commit, post a hash, or better insert a GitHub link to it.
