Re: [RFC] Native access to Git LFS cache
- From
Duy Nguyen <pclouds@gmail.com>
- Date
- Jun 28, 2016, 13:11 UTC
- Message-ID
- <CACsJy8DCovHoutyEYwaxdCTU4K-h8u_JTOwt8GUiNTkkXzGz3w@mail.gmail.com>
- In-Reply-To
- <alpine.DEB.2.20.1606281139490.12947@virtualbox>
On Tue, Jun 28, 2016 at 11:40 AM, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
Show 20 quoted lines
> Hi Duy, > > On Mon, 27 Jun 2016, Duy Nguyen wrote: > >> On Mon, Jun 27, 2016 at 7:38 AM, <larsxschneider@gmail.com> wrote: >> > ## Proposed solution >> > Git LFS caches its objects under .git/lfs/objects. Most of the time >> > Git LFS objects are already available in the cache (e.g. if you switch >> > branches back and forth). I implemented these "cache hits" natively in >> > Git. Please note that this implementation is just a quick and dirty >> > proof of concept. If the Git community agrees that this kind of >> > approach would be acceptable then I will start to work on a proper >> > patch series with cross platform support and unit tests. >> >> Would it be possible to move all this code to a separate daemon? >> Instead of spawning a new process to do the filtering, you send a >> command "convert this" over maybe unix socket and either receive the >> whole result over the socket, or receive a path of the result. > > Unix sockets are not really portable...
It's the same situation as index-helper. I expect you guys will replace the transport with named pipe or similar.
-- Duy