git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: larsxschneider@gmail.com
To: git@vger.kernel.org
Cc: luke@diamand.org, Lars Schneider <larsxschneider@gmail.com>
Subject: [PATCH v1 0/2] git-p4: fix Git LFS pointer parsing
Date: Tue, 19 Apr 2016 22:08:48 +0200	[thread overview]
Message-ID: <1461096530-82448-1-git-send-email-larsxschneider@gmail.com> (raw)

From: Lars Schneider <larsxschneider@gmail.com>

Travis-CI uses 'brew' to always install the latest available version of
Git LFS on the OS X build machines (on Linux the version is sticky).
A change in Git LFS 1.2.0 [1] breaks the git-p4 LFS integration [2].

This mini series updates Travis-CI to the latest Git-LFS and Perforce
versions on Linux and Mac and makes git-p4 work with the latest Git LFS
again.

Thanks,
Lars

[1] https://github.com/github/git-lfs/pull/1105
[2] https://travis-ci.org/git/git/jobs/124047942

Lars Schneider (2):
  travis-ci: update Git-LFS and P4 to the latest version
  git-p4: fix Git LFS pointer parsing

 .travis.yml              | 4 ++--
 Documentation/git-p4.txt | 3 ++-
 git-p4.py                | 6 +++---
 3 files changed, 7 insertions(+), 6 deletions(-)

--
2.5.1

             reply	other threads:[~2016-04-19 20:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-19 20:08 larsxschneider [this message]
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
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

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

  git send-email \
    --in-reply-to=1461096530-82448-1-git-send-email-larsxschneider@gmail.com \
    --to=larsxschneider@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=luke@diamand.org \
    /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).