git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luke Diamand <luke@diamand.org>
To: Lars Schneider <larsxschneider@gmail.com>
Cc: Git Users <git@vger.kernel.org>, technoweenie@github.com
Subject: Re: [RFC PATCH] git-p4: add option to store files in Git LFS on import
Date: Sun, 30 Aug 2015 09:49:22 +0100	[thread overview]
Message-ID: <CAE5ih7-TfLqwye8YpmZz90AVjYGQ8m0sF6GLKnG9pjvV8cTSjw@mail.gmail.com> (raw)
In-Reply-To: <1440764691-62254-1-git-send-email-larsxschneider@gmail.com>

On 28 August 2015 at 13:24,  <larsxschneider@gmail.com> wrote:
> 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.

I'm a bit worried by this. LFS isn't the only way to handle large
files in git - there's also git annex (which I've used in a similar
situation) and obviously random homebrew solutions. We're going to end
up with git-p4 sprouting ever increasing numbers of
--use-XXX-if-size-exceeds options. On the other hand, having it
integrated into git-p4 is quite nice as it saves a lot of messing
around.

Would it be possible as a start to have (within git-p4) a generic
spot-big-files-and-handle-them-differently patch, and a second patch
to add specific LFS support? That then means that other schemes would
be a lot easier to add in future.

Some other comments inline.

>
> 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)

Can you switch to a newer git - this one's quite old now so if there
are regressions introduced later, you won't know about them!

>

  parent reply	other threads:[~2015-08-30  8:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-28 12:24 [RFC PATCH] git-p4: add option to store files in Git LFS on import larsxschneider
2015-08-28 12:24 ` larsxschneider
2015-08-30  9:08   ` Luke Diamand
2015-08-30  8:49 ` Luke Diamand [this message]
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

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

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