to go.
Agree. It's less than optimal but I think it's something that we all
could live with. Deciding to switching the default (or not) is then
rightfully postponed to a later time, and we can revisit the pros and
cons then. The important thing now is to get the functionality
implemented in a good way, tested and eventually merged.
--
Per Lundberg
cs for "git
clean -dfx" _as long as we update the help text_ so that "-x" indicates
more clearly that non-trashable files can be deleted. It doesn't make
things _worse_ than they currently are and if this is what it takes to
get the trashable concept implemented and accepted by the community,
it's a compromise I'd be willing to make.
--
Per Lundberg
idea to have a "mix" of both
trashable and precious. IMO, we should try to find which one of these
concepts suits most general use cases best and causes less churn for
existing scripts/users' existing "semantic expectations", and pick that one.
--
Per Lundberg
nclude very clear notices
of this in the release notes. The config flag is retained, but its
default changes from true->false or vice versa. People who dislike the
new behavior can easily change back to the 2.x semantics.
Would this be a reasonable compromise for everybody?
--
Per Lundberg
the "precious" setting.
(I also think "trashable" sounds better and is more clear & precise than
"precious", for whatever that is worth.)
--
Per Lundberg
Hi,
Sorry if this question has been asked before; I skimmed through the list
archives and the FAQ but couldn't immediately find it - please point me
in the right direction if it has indeed been discussed before.
We were renaming some previously-included configuration files (foo.conf)
in one
6 matches
Mail list logo
