Graph log - follow history across copies and renames

[Mads Kiilerich]

Stanimir Stamenkov wrote, On 11/27/2010 11:49 PM:
> I have a file renamed/moved at some point and I issue:
>
> hg glog my_file
>
> The log normally stops at the revision the file was renamed/moved. As 
> far as I've observed the glog command doesn't have a --follow option 
> as the normal log command has.  Is there a technical limitation the 
> glog command doesn't have a --follow option, or it is just not 
> implemented?
>

I would say both. There is a technical limitation with graphlog and 
following filenames, and the workaround or --follow haven't been 
implemented.

Graphlog always visualizes the changelog graph. If a filename is 
specified graphlog will only show the changesets from that files 
filelog, but it will use the graph structure from the changelog. The 
result is perhaps not what you want. A visualization of the filelog 
would be more interesting (especially if it is without issue 1327 
issues). The --follow option to log makes it follow the filelog, but 
graphlog don't know how to do the same.

Matt has mentioned that he would like to replace the "log --follow" 
machinery with the "new" revsets, but I can imagine that --follow is one 
thing that makes it tricky. He also mentioned that he would like to 
introduce "filesets". I guess --follow combines these two concepts in an 
interesting way.

/Mads