Re: [PATCH v1 2/2] git-p4: fix Git LFS pointer parsing

From: Sebastian Schuberth <sschuberth@gmail.com>
Date: Apr 20, 2016, 15:40 UTC
Message-ID: <CAHGBnuOAsKNDc7UBN=1r867KxpRSr_RG+EPFhCL+gJbbQo9rdg@mail.gmail.com>
In-Reply-To: <xmqqy488wb4p.fsf@gitster.mtv.corp.google.com>

On Wed, Apr 20, 2016 at 5:30 PM, Junio C Hamano <gitster@pobox.com> wrote:

Show 8 quoted lines

>> If clients rely on output targeted at human consumption it's not
>> surprising that these clients need to be adjusted from time to time.
>> What's troubling is not the change to git-lfs, but the very un-generic
>> way git-p4 is implemented.
>
> Sounds like the subcommand they are using is not meant for
> scripting?  What is the kosher way to get at the information they
> can use that is a supported interface for scripters?

The "pointer" subcommand indeed is listed under "Low level commands" by "git lfs" (without any arguments), and as such it probably can be considered for scripting use. However, before my fix in [1] the subcommand was printing both output targeted at humans and output targeted at scripts to stdout. After my fix, only output targeted at script goes to stdout, and output targeted at humans goes to stderr.

[1] https://github.com/github/git-lfs/pull/1105

-- 
Sebastian Schuberth