[Top][All Lists]

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

Re: base

From: David Kastrup
Subject: Re: base
Date: Thu, 26 Aug 2010 17:28:57 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux)

Óscar Fuentes <address@hidden> writes:

> Eli Zaretskii <address@hidden> writes:
>> So you are saying that there's no way a user can understand how to use
>> git efficiently without knowing about SHA1, hashes, blobs, index
>> files, and how they all live happily in disk files and point to one
>> another?
> It is perfectly possible to use git without knowing its model, in the
> sense that you can store your changes on the repo, see logs, etc. More
> or less like CVS or Subversion (or Bazaar!) where the user knows recipes
> for dealing with a restricted, mostly simplistic, set of
> requirements. On the long term (or not so long) it is not the most
> cost-effective approach.
> For any dVCS, revision IDs are a core concept. A user that doesn't
> understand revision IDs eventually will suffer the consequences of his
> ignorance. That applies to git's SHA1 hashes and to whatever bzr uses as
> IDs. Blobs and trees are on the foundations of git and defines how it
> stores information. Having some knowledge about them makes easy to
> understand why git does not track empty directories,

Actually, it doesn't make it easy to understand.  After all, git tracks
symbolic links which have as little information beside the entry itself
as directory entries do.

It would be easy for git to make an additional entry for the directory
entry itself.

David Kastrup

reply via email to

[Prev in Thread] Current Thread [Next in Thread]