Re: Using git-update-index to add existing tree objects at other paths

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Chris Torek <chris.torek@xxxxxxxxx> writes:

> On Tue, Oct 4, 2022 at 7:43 AM Sean Allred <allred.sean@xxxxxxxxx> wrote:
>> ... but the following does not work:
>>
>>     $ cat | git update-index --index-info
>>     040000 tree TREEID1 PATH1
>
> The index is not designed to hold tree objects (at least not at this level),
> and update-index should be fed only the full path names of files, symbolic
> links (mode 120000), or gitlinks (mode 160000).

Correct.

With the ongoing "sparse-index" work, it may not be an entirely
unreasonable idea to extend the "update-index" command to allow
it adding a tree entry there (after removing the entries that are
for anything that fall inside that directory), but we are not there
yet, in the sense that we haven't even discussed if doing it at this
level is a reasonable thing to do.



[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux