Junio C Hamano <gits...@pobox.com> writes:

> One thing I noticed about Jonathan's warn_pathless_add() thing is
> that even though it knows for which path we would behave differently
> between the current version and Git 2.0, the warning message does
> not say which path outside the current directory would be added if
> not restricted with an explicit ".", and leaves the reader in
> suspense.
> We may want to fix it by tweaking the end of the message, perhaps?

Hmph, bad idea.

At the point of calling warn_pathless_add(), it seems that we are
triggering this for paths that are not necessarily modified when run
with "add -n -u".
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to