Re: "git add -u" broken in git 1.7.4?

From: Junio C Hamano <gitster@pobox.com>
Date: Feb 10, 2011, 02:46 UTC
Message-ID: <7vd3n061yp.fsf@alter.siamese.dyndns.org>
In-Reply-To: <20110210023132.GB5073@sigill.intra.peff.net>

Jeff King <peff@peff.net> writes:

> ls-tree already has --full-tree (and --full-name, which just gives full
> pathnames but still restricts output to files in the current directory).
> ls-files. ls-files has --full-name, but AFAIK needs a matching
> --full-tree.

... and --no-full-tree, if we were to make the default tweakable from the configuration mechanism for Porcelain commands. The convoluted logic would go like this:

 1. 'git clean' can be made default to the full-tree operation by
    setting "porcelain.fullTreeOnNoPathspec = yes";

 2. a script may want to defeat random configuration the user may have and
    'git clean --full-tree' and 'git clean --no-full-tree' are the ways to
    force the semantics it wants;

 3. 'git ls-files' will keep the default of cwd-relativeness, but will gain
    'git ls-files --full-tree'; naturally people expect --no-full-tree to
    work, even though the command will not be affected by the configuration
    variable porcelain.fullTreeOnNoPathspec.