https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252664
--- Comment #1 from Ed Maste <[email protected]> --- It comes from standard git terminology, e.g. from `git describe` --dirty[=<mark>], --broken[=<mark>] Describe the state of the working tree. When the working tree matches HEAD, the output is the same as "git describe HEAD". If the working tree has local modification "-dirty" is appended to it. If a repository is corrupt and Git cannot determine if there is local modification, Git will error out, unless `--broken' is given, which appends the suffix "-broken" instead. Perhaps we could use e.g. --dirty=-modified or such. Separately, one of the advantages of git is that you can track any local changes, so I'd suggest committing all changes in place on a system that innocent end users would connect to. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "[email protected]"
