Re: newbie questions about git design and features (some wrt hg)
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Feb 1, 2007, 10:49 UTC
- Message-ID
- <Pine.LNX.4.63.0702011149290.22628@wbgn013.biozentrum.uni-wuerzburg.de>
- In-Reply-To
- <45C1BDD3.8050103@fs.ei.tum.de>
Hi,
On Thu, 1 Feb 2007, Simon 'corecode' Schubert wrote:
Show 11 quoted lines
> Johannes Schindelin wrote: > > > 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