What we are seeing is an issue after we do a file move to a new directory. Once moved, the previous history of the file is not readily available. One needs to know to use --follow on the command line, and worse, gitweb does not show the full history at all. We have almost a decade of history on the project, from several different source control systems. We often find it useful to go back and find out when something changed, so we want to keep it and have it easily available. >-----Original Message----- >From: Alex Riesen [mailto:raa.lkml@xxxxxxxxx] >Sent: Friday, October 24, 2008 2:43 PM >To: Moore, Robert >Cc: Michael J Gruber; Lin, Ming M; git@xxxxxxxxxxxxxxx >Subject: Re: git history and file moves > >2008/10/24 Moore, Robert <robert.moore@xxxxxxxxx>: >> Here's what we have: >> >> /var/www/cgi-bin/gitweb.acpica/gitweb.conf >> >> Containts this : GITWEB_CSS = "/icons/gitweb.css"; >> >> What should we add to automatically get all file history? >> > >Nothing. It is the default. You can change the variable Michael >mentioned to use "-M -M -C -C" but it is very-very slow on any >kind of history worth its commits. > >And you almost never talk about _file_ history in Git. It is all >_project_ history, filtered for commits which touch the file you're >interested in at the moment of looking. -- 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
