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

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

From
Sebastian Schuberth <sschuberth@gmail.com>
Date
Apr 22, 2016, 07:55 UTC
Message-ID
<CAHGBnuN_Tck3TY0DO38HpXLbe5mew-76Y0okaxmJtGEGs2g04A@mail.gmail.com>
In-Reply-To
<780ED4D6-AD96-4BAF-A522-C724C3938EED@gmail.com>

On Fri, Apr 22, 2016 at 9:53 AM, Lars Schneider <larsxschneider@gmail.com> wrote:

> What would be the best way forward? A v3 with a better commit message
> mentioning the array -> string change?
I'd vote for that, yes. Also v3 could then properly incorporate my regexp.
-- 
Sebastian Schuberth
Previous: Lars Schneider
Message 9 of 9 in “git-p4: fix Git LFS pointer parsing”
  1. 0/2 git-p4: fix Git LFS pointer parsinglarsxschneider@gmail.com, Apr 20, 2016
  2. 1/2 travis-ci: update Git-LFS and P4 to the latest versionlarsxschneider@gmail.com, Apr 20, 2016
  3. 2/2 git-p4: fix Git LFS pointer parsinglarsxschneider@gmail.com, Apr 20, 2016
  4. Sebastian SchuberthApr 20, 2016
  5. Junio C HamanoApr 20, 2016
  6. Lars SchneiderApr 20, 2016
  7. Junio C HamanoApr 20, 2016
  8. Lars SchneiderApr 22, 2016
  9. Sebastian SchuberthApr 22, 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.