git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: larsxschneider@gmail.com
To: git@vger.kernel.org
Cc: sschuberth@gmail.com, gitster@pobox.com, ben.woosley@gmail.com,
	Lars Schneider <larsxschneider@gmail.com>
Subject: [PATCH v3 0/3] git-p4: fix Git LFS pointer parsing
Date: Sun, 24 Apr 2016 20:58:09 +0200	[thread overview]
Message-ID: <1461524292-20490-1-git-send-email-larsxschneider@gmail.com> (raw)

From: Lars Schneider <larsxschneider@gmail.com>

v1: $gmane/291917
v2: $gmane/291991

diff to v2:
 * use regex to parse "oid" instead of a complicated split logic
   ($gmane/291995, thanks Sebastian)
 * add a note to the commit message emphasizing the change from array
   to string in the second return parameter ($gmane/292077, thanks Junio)
 * detect the Git-LFS preamble by the constant first part of the string
   ($gmane/292079, thanks Ben)
 * change the name of the Git-LFS and Perforce version variables to
   express that they are only used in the Linux build

Thanks,
Lars

Lars Schneider (3):
  travis-ci: update Git-LFS and P4 to the latest version
  travis-ci: express Linux/OS X dependency versions more clearly
  git-p4: fix Git LFS pointer parsing

 .travis.yml               | 17 ++++++++++-------
 git-p4.py                 | 13 ++++++++++---
 t/t9824-git-p4-git-lfs.sh |  4 ++++
 3 files changed, 24 insertions(+), 10 deletions(-)

--
2.5.1

             reply	other threads:[~2016-04-24 18:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-24 18:58 larsxschneider [this message]
2016-04-24 18:58 ` [PATCH v3 1/3] travis-ci: update Git-LFS and P4 to the latest version larsxschneider
2016-04-24 18:58 ` [PATCH v3 2/3] travis-ci: express Linux/OS X dependency versions more clearly larsxschneider
2016-04-25  4:40   ` Eric Sunshine
2016-04-25  7:05     ` Lars Schneider
2016-04-24 18:58 ` [PATCH v3 3/3] git-p4: fix Git LFS pointer parsing larsxschneider
2016-04-24 19:16   ` Sebastian Schuberth
2016-04-25  7:33     ` Lars Schneider
2016-04-25  7:35       ` Sebastian Schuberth

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1461524292-20490-1-git-send-email-larsxschneider@gmail.com \
    --to=larsxschneider@gmail.com \
    --cc=ben.woosley@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --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.
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 NNTP newsgroup(s).