Re: Understanding Git Under The Hood: Trees

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

 



On Thu, Aug 15, 2013 at 7:31 PM, Junio C Hamano <gitster@xxxxxxxxx> wrote:
> While the last statement applies to other parts of the system, it is
> not true for the in-core index design.  We always had a flat index,
> and it is not cheating at all.  The original "tree" was also a flat
> representation of everything under the sun, and hierarchical tree
> objects came much later.

To some degree that revalidates my interpretation of Andreas'
statements. If I understand it correctly eacht time a shell command is
executed, which requires tree interaction, the corresponding tree is
read from filesystem to memory completely before anything is done? So
if I git-add a file, the whole index is read first, then the memory
object is changed and then the resulting change is written to disk
bottom-up from the point of view of the tree?
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[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]