From: larsxschneider@gmail.com
To: git@vger.kernel.org
Cc: luke@diamand.org, Lars Schneider <larsxschneider@gmail.com>
Subject: [PATCH v4 0/5] git-p4: add support for large file systems
Date: Wed, 9 Sep 2015 13:59:05 +0200 [thread overview]
Message-ID: <1441799950-54633-1-git-send-email-larsxschneider@gmail.com> (raw)
From: Lars Schneider <larsxschneider@gmail.com>
Diff to v3:
* add large file system mock class for testing (Thanks Luke!)
* add early exit for compressed threshold: If a file is smaller then the threshold then we don't need to compress it.
Thanks,
Lars
Lars Schneider (5):
git-p4: add optional type specifier to gitConfig reader
git-p4: add gitConfigInt reader
git-p4: return an empty list if a list config has no values
git-p4: add support for large file systems
git-p4: add Git LFS backend for large file system
Documentation/git-p4.txt | 28 +++++
git-p4.py | 223 +++++++++++++++++++++++++++++++++++++---
t/t9823-git-p4-mock-lfs.sh | 106 +++++++++++++++++++
t/t9824-git-p4-git-lfs.sh | 249 +++++++++++++++++++++++++++++++++++++++++++++
4 files changed, 593 insertions(+), 13 deletions(-)
create mode 100755 t/t9823-git-p4-mock-lfs.sh
create mode 100755 t/t9824-git-p4-git-lfs.sh
--
2.5.1
next reply other threads:[~2015-09-09 11:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-09 11:59 larsxschneider [this message]
2015-09-09 11:59 ` [PATCH v4 1/5] git-p4: add optional type specifier to gitConfig reader larsxschneider
2015-09-09 11:59 ` [PATCH v4 2/5] git-p4: add gitConfigInt reader larsxschneider
2015-09-09 11:59 ` [PATCH v4 3/5] git-p4: return an empty list if a list config has no values larsxschneider
2015-09-09 11:59 ` [PATCH v4 4/5] git-p4: add support for large file systems larsxschneider
2015-09-09 17:20 ` Junio C Hamano
2015-09-09 20:09 ` Lars Schneider
2015-09-09 20:44 ` Junio C Hamano
2015-09-09 11:59 ` [PATCH v4 5/5] git-p4: add Git LFS backend for large file system larsxschneider
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=1441799950-54633-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).