git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 20, 2016, 15:30 UTC
Message-ID
<xmqqy488wb4p.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<CAHGBnuOuFYvf=CSyCLbhn7pyq4jsqH+p+xV9rxAtU1y3r+qjzw@mail.gmail.com>
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?

Previous: Sebastian SchuberthNext: Sebastian Schuberth
Message 8 of 13 in “git-p4: fix Git LFS pointer parsing”
  1. 0/2 git-p4: fix Git LFS pointer parsinglarsxschneider@gmail.com, Apr 19, 2016
  2. 1/2 travis-ci: update Git-LFS and P4 to the latest versionlarsxschneider@gmail.com, Apr 19, 2016
  3. 2/2 git-p4: fix Git LFS pointer parsinglarsxschneider@gmail.com, Apr 19, 2016
  4. Junio C HamanoApr 19, 2016
  5. Lars SchneiderApr 19, 2016
  6. Junio C HamanoApr 19, 2016
  7. Sebastian SchuberthApr 20, 2016
  8. Junio C HamanoApr 20, 2016
  9. Sebastian SchuberthApr 20, 2016
  10. t9824: fix broken &&-chain in a subshellSZEDER Gábor, Apr 24, 2016
  11. Lars SchneiderApr 24, 2016
  12. SZEDER GáborApr 24, 2016
  13. Lars SchneiderApr 24, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.