> On 13 Dec 2016, at 18:20, Christian Couder wrote:
>
> On Sat, Dec 3, 2016 at 7:47 PM, Lars Schneider
> wrote:
>>
>>> On 30 Nov 2016, at 22:04, Christian Couder
>>> wrote:
>>>
>>> Goal
>>>
>>>
>>> Git can store its objects only in the form of loose objects in
>>> separate files or p
On Tue, Dec 13, 2016 at 9:05 PM, Junio C Hamano wrote:
> Christian Couder writes:
>
>> In general I think that having a lot of refs is really a big problem
>> right now in Git as many big organizations using Git are facing this
>> problem in one form or another.
>> So I think that support for a b
Christian Couder writes:
> In general I think that having a lot of refs is really a big problem
> right now in Git as many big organizations using Git are facing this
> problem in one form or another.
> So I think that support for a big number of refs is a separate and
> important problem that sh
On Sat, Dec 3, 2016 at 7:47 PM, Lars Schneider wrote:
>
>> On 30 Nov 2016, at 22:04, Christian Couder
>> wrote:
>>
>> Goal
>>
>>
>> Git can store its objects only in the form of loose objects in
>> separate files or packed objects in a pack file.
>>
>> To be able to better handle some kind
On Wed, Nov 30, 2016 at 11:36 PM, Junio C Hamano wrote:
> Christian Couder writes:
>
>> For now there should be one odb ref per blob. Each ref name should be
>> refs/odbs// where is the sha1 of the blob stored
>> in the external odb named .
>>
>> These odb refs should all point to a blob that sh
On Sat, Dec 03, 2016 at 07:47:51PM +0100, Lars Schneider wrote:
> > - " have": the command should output the sha1, size and
> > type of all the objects the external ODB contains, one object per
> > line.
>
> This looks impractical. If a repo has 10k external files with
> 100 versions each then y
> On 30 Nov 2016, at 22:04, Christian Couder wrote:
>
> Goal
>
>
> Git can store its objects only in the form of loose objects in
> separate files or packed objects in a pack file.
>
> To be able to better handle some kind of objects, for example big
> blobs, it would be nice if Git could
Christian Couder writes:
> For now there should be one odb ref per blob. Each ref name should be
> refs/odbs// where is the sha1 of the blob stored
> in the external odb named .
>
> These odb refs should all point to a blob that should be stored in the
> Git repository and contain information ab
Goal
Git can store its objects only in the form of loose objects in
separate files or packed objects in a pack file.
To be able to better handle some kind of objects, for example big
blobs, it would be nice if Git could store its objects in other object
databases (ODB).
To do that, this pat
9 matches
Mail list logo
