From: Ben Peart <peartben@gmail.com>
To: "Duy Nguyen" <pclouds@gmail.com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>,
Ben Peart <benpeart@microsoft.com>
Subject: Re: [RFC v1] Add virtual file system settings and hook proc
Date: Mon, 5 Nov 2018 15:07:48 -0500 [thread overview]
Message-ID: <b0518222-f0ba-a613-6a54-ad7f66d56140@gmail.com> (raw)
In-Reply-To: <CACsJy8Coyw-yiumAfTeASSPdzWXeRgtrS8Ta-VtYph4QnPunVQ@mail.gmail.com>
On 11/5/2018 10:26 AM, Duy Nguyen wrote:
> On Mon, Nov 5, 2018 at 12:40 PM Ævar Arnfjörð Bjarmason
> <avarab@gmail.com> wrote:
>>
>>
>> On Sun, Nov 04 2018, Duy Nguyen wrote:
>>
>>> On Wed, Oct 31, 2018 at 9:53 PM Ben Peart <peartben@gmail.com> wrote:
>>>>>> +core.virtualFilesystem::
>>>>>> + If set, the value of this variable is used as a command which
>>>>>> + will identify all files and directories that are present in
>>>>>> + the working directory. Git will only track and update files
>>>>>> + listed in the virtual file system. Using the virtual file system
>>>>>> + will supersede the sparse-checkout settings which will be ignored.
>>>>>> + See the "virtual file system" section of linkgit:githooks[6].
>>>>>
>>>>> It sounds like "virtual file system" is just one of the use cases for
>>>>> this feature, which is more about a dynamic source of sparse-checkout
>>>>> bits. Perhaps name the config key with something along sparse checkout
>>>>> instead of naming it after a use case.
>>>>
>>>> It's more than a dynamic sparse-checkout because the same list is also
>>>> used to exclude any file/folder not listed. That means any file not
>>>> listed won't ever be updated by git (like in 'checkout' for example) so
>>>> 'stale' files could be left in the working directory. It also means git
>>>> won't find new/untracked files unless they are specifically added to the
>>>> list.
>>>
>>> OK. I'm not at all interested in carrying maintenance burden for some
>>> software behind closed doors. I could see values in having a more
>>> flexible sparse checkout but this now seems like very tightly designed
>>> for GVFS. So unless there's another use case (preferably open source)
>>> for this, I don't think this should be added in git.git.
>>
>> I haven't looked at the patch in any detail beyond skimming it, and
>> you're more familiar with this area...
>>
>> But in principle I'm very interested in getting something like this in
>> git.git, even if we were to assume GVFS was a 100% proprietary
>> implementation.
>
> I have nothing against building a GVFS-like solution. If what's
> submitted can be the building blocks for that, great! But if it was
> just for GVFS (and it was not available to everybody) then no thank
> you.
>
Not only is VFS for Git open source and is/will be supported on Windows,
Mac and Linux, the interface being proposed is quite generic so should
be usable for other implementations.
To use it, you just need to provide a hook that will return a list of
files git should pay attention to (using a subset of the existing
sparse-checkout format).
If you see anything that would make using it difficult for other
solutions to use, let's fix it now!
next prev parent reply other threads:[~2018-11-05 20:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-30 19:16 [RFC v1] Add virtual file system settings and hook proc Ben Peart
2018-10-30 23:07 ` Junio C Hamano
2018-10-31 20:12 ` Ben Peart
2018-11-05 0:02 ` Junio C Hamano
2018-11-05 20:00 ` Ben Peart
2018-10-31 19:11 ` Duy Nguyen
2018-10-31 20:53 ` Ben Peart
2018-11-04 6:34 ` Duy Nguyen
2018-11-04 21:01 ` brian m. carlson
2018-11-05 15:22 ` Duy Nguyen
2018-11-05 20:18 ` Ben Peart
2018-11-05 20:27 ` Ben Peart
2018-11-05 11:40 ` Ævar Arnfjörð Bjarmason
2018-11-05 15:26 ` Duy Nguyen
2018-11-05 20:07 ` Ben Peart [this message]
2018-11-05 21:53 ` Johannes Schindelin
2018-11-27 19:50 ` [PATCH v1] teach git to support a virtual (partially populated) work directory Ben Peart
2018-11-28 13:31 ` SZEDER Gábor
2018-11-29 14:09 ` Ben Peart
2018-12-13 19:41 ` [PATCH v2] " Ben Peart
2019-01-28 19:00 ` Ben Peart
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=b0518222-f0ba-a613-6a54-ad7f66d56140@gmail.com \
--to=peartben@gmail.com \
--cc=avarab@gmail.com \
--cc=benpeart@microsoft.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@gmail.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.
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).