From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <366E22CB4C99DA10789C85BE86B6DD95@eigenstate.org>
To: driusan@gmail.com, 9fans@9fans.net
Date: Tue,  2 Apr 2019 08:35:17 -0700
From: ori@eigenstate.org
In-Reply-To: CAG2UyHohky418z0_85=rT=BLSLe+oj7F8bNwk+cZxEC7LCypuw@mail.gmail.com
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] Git/fs: Possibly Usable
Topicbox-Message-UUID: f8619a7e-ead9-11e9-9d60-3106f5b1d025

> On Tue, Apr 2, 2019 at 12:49 AM <ori@eigenstate.org> wrote:
>> One caveat I have: Git's index file format is a bit
>> boneheaded, so I'm ignoring it. The index doesn't affect
>> the wire protocol, so this isn't an interoperability issue,
>> unless you share the same physical repository on both
>> Plan 9 and Unix. If you do, expect them to get out of
>> sync on uncommitted but added files.
>>
>
> What problems did you have with the index format? In my experience
> it was relatively sane (relative to the pack protocol/format, I mean,
> which is a pretty low bar to set.)

It's easy to implement, but the tool is more useful without it.
The concept of staged files that it implies makes git clunkier
to use.

The index would also require a special tool to manipulate it,
which makes manipulating it from a script much clunkier.