Hi, On Fri, 12 Oct 2007, Peter Karlsson wrote: > > But don't you see? When switching branches, this totally breaks down. > > Why would it? If the file is the same on both branches, nothing would > happen (it is still the same version), and if the file is different, it > gets changed anyway, and a new keyword expansion would take place. Finding out which commit last changed that file is slow. That's why it breaks down. It is possible, yes. But then I think that you really do not want this. You are just to used to CVS/SVN to see that there is a much better way in git. > > No, really, IMHO it is enough to show either the commit name or the > > blob name of the file. After all, you are not interested in the date > > that this file was last committed, but in the _contents_. > > Yes, but I want it on the lowest addressable unit size, i.e on the file > level (I could possibly want to have the last commit for a set of files > when I have something that get generated from several sources, but that > is rare for a regular website, unless since javascripts and stylesheets > etc. are delivered separately). The lowest addressable unit size is the file level, alright. And $Id$ contains the blob name. IOW it contains a key to retrieve the contents of exactly this version of the file. Ciao, Dscho - 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
