• Q. Schroll (4/4) Mar 08 2021 When I enter `dmd --version`, it says:
• Paul Backus (3/7) Mar 08 2021 It means someone made a mistake when preparing the release.
• JN (2/9) May 20 2021 v2.096.1 also reports as -dirty
• Norm (6/10) May 22 2021 This comes from `git describe --dirty` and indicates there were

Q. Schroll <qs.il.paperinik gmail.com> writes:

When I enter `dmd --version`, it says:
   DMD64 D Compiler v2.095.1-dirty
What should the "dirty" mean? To me, it seems looks something 
went wrong somewhere.

Paul Backus <snarwin gmail.com> writes:

On Monday, 8 March 2021 at 22:29:58 UTC, Q. Schroll wrote:
 When I enter `dmd --version`, it says:
   DMD64 D Compiler v2.095.1-dirty
 What should the "dirty" mean? To me, it seems looks something 
 went wrong somewhere.

It means someone made a mistake when preparing the release. 
Probably harmless.

JN <666total wp.pl> writes:

On Tuesday, 9 March 2021 at 01:36:18 UTC, Paul Backus wrote:
 On Monday, 8 March 2021 at 22:29:58 UTC, Q. Schroll wrote:
 When I enter `dmd --version`, it says:
   DMD64 D Compiler v2.095.1-dirty
 What should the "dirty" mean? To me, it seems looks something 
 went wrong somewhere.

 It means someone made a mistake when preparing the release. 
 Probably harmless.

v2.096.1 also reports as -dirty

Norm <norm.rowtree gmail.com> writes:

On Monday, 8 March 2021 at 22:29:58 UTC, Q. Schroll wrote:
 When I enter `dmd --version`, it says:
   DMD64 D Compiler v2.095.1-dirty
 What should the "dirty" mean? To me, it seems looks something 
 went wrong somewhere.

This comes from `git describe --dirty` and indicates there were 
uncommitted changes in the repo when the release was built. This 
would raise red flags if seen in a commercial setting and looks a 
bit unprofessional but it is most likely harmless. Probably one 
of the build scripts or unittests are polluting the repo.