Hi,
On Thu, 1 Feb 2007, Simon 'corecode' Schubert wrote:
Johannes Schindelin wrote:
quoted
quoted
If you rename, you take the penalty of duplicating the content
(compressed) with a new name. No big deal there. So there are *no*
file-ids. Blobs go into the data/index file which corresponds to their
filename.
So, can you explain to me how a filename is _not_ a file-id?
It is not a file-id like other SCM use it (I think monotone, not sure though).
If you copy/move the content to a new name, the ID will not stay the same.
Just see it as a hash bucket which allows you easy access to the history for a
file currently with this name.
Ah, thanks. I misunderstood the meaning of file-id in _that_ context.
Ciao,
Dscho