On Dec 11, 2007 8:46 PM, Daniel Barkalow <barkalow@xxxxxxxxxxxx> wrote: > On Tue, 11 Dec 2007, Daniel Berlin wrote: > > > It is stored in an easier format. However, can you not simply provide > > side-indexes to do the annotation? > > > > I guess that own't work in git because you can change history (in > > other scm's, history is readonly so you could know the results for > > committed revisions will never change). > > History in git is read-only. It's just that git lets you fork and move > forward with something different. Each commit can never change (and, in > fact, you'd have to badly break SHA1 to change it), but which commits are > relevant to the history can change. > Well, revisions never change, but history intended as revision's parent information could and do changes when you use a path delimiter. So does the graph that is a direct visualization of parent information. For a single revision (that modifies say 3 files) you can have at leat 3 different histories and acutally more if you want to visualize also the history of the directories trees that owns the modified files. You end up with a quite big number of different histories all showing your revisions in different ways, according to the path delimiter you use. Perhaps the intended meaning of "changing histories" is this, and in any case is this the reason you cannot (or has no sense to do) "save" a single file history in git. Marco - 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
