Re: git and bzr
- From
- Nicholas Allen <allen@ableton.com>
- Date
- Nov 28, 2006, 17:44 UTC
- Message-ID
- <456C7592.6020700@ableton.com>
- In-Reply-To
- <Pine.LNX.4.64.0611280754050.30076@woody.osdl.org>
Show 5 quoted lines
> > The reason this is a good example is simply the fact that it should > totally silence anybody who still thinks that tracking file identities is > a good thing. It explains well why tracking file identities is just > _stupid_.
I'm unfamiliar with git so I could be totally wrong here!
I know that bzr supports file renames/moves very effectively and I understood that git doesn't support this to the same extent (correct me if I am wrong as I have not used git at all!).
If that is the case, could that be because bzr gives each file its own id and can detect this easily but git's content based approach can't? If so then claiming file identifiers is *stupid* seems a bit extreme. So I would have thought *both* file identifiers and line/content identifiers are needed for tracking changes made to the files and to their contents respectively. When a file is copied then the contents are copied and it is given a new file identifier. When a file is moved it keeps the same identifier. So don't you need file identifiers as well as line/content identifiers?