From: Christian Couder <christian.couder@gmail.com>
To: Lars Schneider <larsxschneider@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, Jon Loeliger <jdl@jdl.com>,
David Bainbridge <david.bainbridge@ericsson.com>,
Jeff King <peff@peff.net>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Git Miniconference at Plumbers
Date: Wed, 14 Sep 2016 18:27:32 +0200 [thread overview]
Message-ID: <CAP8UFD0M8MDs-0UAFgx288XVdWg_XP=bOwAWoXdY=5Sg7pMFsw@mail.gmail.com> (raw)
In-Reply-To: <1019E7FD-0AC0-4BCE-B810-BE20968DFEE9@gmail.com>
On Tue, Sep 13, 2016 at 1:14 AM, Lars Schneider
<larsxschneider@gmail.com> wrote:
>
>> On 12 Sep 2016, at 21:11, Junio C Hamano <gitster@pobox.com> wrote:
>>
>> [..]
>> properly; supporting "huge objects" better in the object layer,
>> without having to resort to ugly hacks like GitLFS that will never
>> be part of the core Git. [...]
>
> I agree with you that GitLFS is an ugly hack.
>
> Some applications have test data, image assets, and other data sets that
> need to be versioned along with the source code.
>
> How would you deal with these kind of "huge objects" _today_?
I think that Junio was saying that this problem and other problems
like this one are indeed itches for some people, but maybe not for
kernel community.
About this specific problem, as you probably know, I started working
on adding support for external object databases, on top of some
previous work that Peff had started some years ago:
https://public-inbox.org/git/20160628181933.24620-1-chriscool@tuxfamily.org/
So if you want to better deal with huge objects in the near future,
you are welcome to help on this.
next prev parent reply other threads:[~2016-09-14 16:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 17:42 Git Miniconference at Plumbers Jon Loeliger
2016-09-12 0:42 ` Jeff King
2016-09-12 13:32 ` Jon Loeliger
2016-09-12 17:53 ` David Bainbridge
2016-09-12 18:09 ` Jon Loeliger
2016-09-12 20:11 ` Junio C Hamano
2016-09-12 23:14 ` Lars Schneider
2016-09-14 16:27 ` Christian Couder [this message]
2016-09-14 17:26 ` Junio C Hamano
2016-09-12 21:23 ` Jakub Narębski
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='CAP8UFD0M8MDs-0UAFgx288XVdWg_XP=bOwAWoXdY=5Sg7pMFsw@mail.gmail.com' \
--to=christian.couder@gmail.com \
--cc=david.bainbridge@ericsson.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jdl@jdl.com \
--cc=larsxschneider@gmail.com \
--cc=peff@peff.net \
/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.
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).