git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed

From: larsxschneider@gmail.com
To: git@vger.kernel.org, luke@diamand.org, technoweenie@github.com
Cc: Lars Schneider <larsxschneider@gmail.com>
Subject: [RFC PATCH] git-p4: add option to store files in Git LFS on import
Date: Fri, 28 Aug 2015 14:24:50 +0200	[thread overview]
Message-ID: <1440764691-62254-1-git-send-email-larsxschneider@gmail.com> (raw)

From: Lars Schneider <larsxschneider@gmail.com>

I am migrating huge Perforce repositories including history to Git. Some of them contain large files that would blow up the resulting Git repositories. This patch adds an option to store these files in Git LFS [1] on git-p4 clone.

In order to run the unit tests you need to install the Git LFS extension [2].

Known limitations:
The option "use-lfs-if-size-exceeds" looks at the uncompressed file size. Sometimes huge XML files are tiny if compressed. I wonder if there is an easy way to learn about the size of a file in a git pack file. I assume compressing it is the only way to know.

Feedback is highly appreciated.

Thank you,
Lars


[1] https://git-lfs.github.com/
[2] https://github.com/github/git-lfs/releases/

Lars Schneider (1):
  git-p4: add option to store files in Git LFS on import

 Documentation/git-p4.txt |  12 ++
 git-p4.py                |  94 ++++++++++++++--
 t/t9822-git-p4-lfs.sh    | 277 +++++++++++++++++++++++++++++++++++++++++++++++
 3 files changed, 374 insertions(+), 9 deletions(-)
 create mode 100755 t/t9822-git-p4-lfs.sh

--
1.9.5 (Apple Git-50.3)

next             reply	other threads:[~2015-08-28 12:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-28 12:24 larsxschneider [this message]
2015-08-28 12:24 ` [RFC PATCH] git-p4: add option to store files in Git LFS on import larsxschneider
2015-08-30  9:08   ` Luke Diamand
2015-08-30  8:49 ` Luke Diamand
2015-08-30 10:18   ` Lars Schneider
2015-08-30 16:36     ` Luke Diamand
2015-09-03  9:40       ` Lars Schneider
2015-09-03 10:07         ` Luke Diamand
2015-09-03 10:12         ` John Keeping

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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=1440764691-62254-1-git-send-email-larsxschneider@gmail.com \
    --to=larsxschneider@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=luke@diamand.org \
    --cc=technoweenie@github.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

Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).