On Mon, Dec 10, 2007 at 05:27:17PM -0800, Junio C Hamano wrote:
> > I suspect there are still some bugs lurking in there, but it's hard
> > to say because I don't know what the behavior _should_ be (there are
> > some test cases in that email).
>
> The last time I looked at the "directory" side of builtin-clean.c, I had
> to quickly reach for my barf bag. I never use "git clean" without "-n"
> and I never ever use "git clean" with "-d"; I do not have any idea what
> behaviour when given "-d" would be useful. AFAIU, the scripted version
> did not have clear semantics either.
I had the same feeling. I am tempted to leave it, then. The
non-intuitive behavior I managed to trigger was:
- _only_ when using git pathspec matching like "git clean -n '*.ext'"
- confusing in a safe way (trying to remove 'dir.ext' with '*.ext'
will accidentally not happen, rather than accidentally happening)
So unless somebody complains, it is probably not a big problem,
and I think fixing it will require mucking with pathspec and dir
matching internals, which would be nice not to do right before v1.5.4.
OTOH, leaving something that is broken and just hoping nobody will
complain feels kind of wrong. :)
-Peff
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
