From: Junio C Hamano <gitster@pobox.com>
To: Sebastian Schuberth <sschuberth@gmail.com>
Cc: Lars Schneider <larsxschneider@gmail.com>,
Git Mailing List <git@vger.kernel.org>,
luke@diamand.org
Subject: Re: [PATCH v1 2/2] git-p4: fix Git LFS pointer parsing
Date: Wed, 20 Apr 2016 08:30:46 -0700 [thread overview]
Message-ID: <xmqqy488wb4p.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CAHGBnuOuFYvf=CSyCLbhn7pyq4jsqH+p+xV9rxAtU1y3r+qjzw@mail.gmail.com> (Sebastian Schuberth's message of "Wed, 20 Apr 2016 10:32:38 +0200")
Sebastian Schuberth <sschuberth@gmail.com> writes:
> 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?
next prev parent reply other threads:[~2016-04-20 15:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 20:08 [PATCH v1 0/2] git-p4: fix Git LFS pointer parsing larsxschneider
2016-04-19 20:08 ` [PATCH v1 1/2] travis-ci: update Git-LFS and P4 to the latest version larsxschneider
2016-04-19 20:08 ` [PATCH v1 2/2] git-p4: fix Git LFS pointer parsing larsxschneider
2016-04-19 20:30 ` Junio C Hamano
2016-04-19 20:54 ` Lars Schneider
2016-04-19 21:04 ` Junio C Hamano
2016-04-20 8:32 ` Sebastian Schuberth
2016-04-20 15:30 ` Junio C Hamano [this message]
2016-04-20 15:40 ` Sebastian Schuberth
2016-04-24 11:50 ` [PATCH] t9824: fix broken &&-chain in a subshell SZEDER Gábor
2016-04-24 16:29 ` Lars Schneider
2016-04-24 16:37 ` SZEDER Gábor
2016-04-24 16:50 ` Lars Schneider
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqy488wb4p.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=larsxschneider@gmail.com \
--cc=luke@diamand.org \
--cc=sschuberth@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).