https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252664
Ulrich Spörlein changed:
What|Removed |Added
Resolution|--- |FIXED
Status|Open
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252664
--- Comment #3 from Helge Oldach ---
(In reply to Ulrich Spörlein from comment #2)
The connotation of "dirty" is pretty different in real life than in git.
I'm not feeling intimidated keeping it as is but then we might as well keep
"blackl
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252664
--- Comment #2 from Ulrich Spörlein ---
This is used in the git and Linux world, so roughly everywhere. Why is this a
problem for FreeBSD users, but not for Linux users?
As Ed mentioned, if this is more like a "permanent" modification, the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252664
--- Comment #1 from Ed Maste ---
It comes from standard git terminology, e.g. from `git describe`
--dirty[=], --broken[=]
Describe the state of the working tree. When the working tree
matches HEAD, the output i
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252664
Li-Wen Hsu changed:
What|Removed |Added
CC||ema...@freebsd.org,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252664
Bug ID: 252664
Summary: change "-dirty" uname -v designator to something less
obtrusive
Product: Base System
Version: Unspecified
Hardware: Any
OS: An
