Hi, Could you please create an issue about the possibility to disable the inclusion of --follow? This is the issue tracker: https://bitbucket.org/mercurialeclipse/main/issues
I'll be defining soon which issues will potentially make it into the next release. Thank you. On Monday, 17 December 2018 15:22:02 UTC+1, Paul Eichhorn wrote: > > Hello Amenel, > > thank you for your reply, I did some digging on your advice. > > The mercurial console uses the command "log --debug --limit 50 --follow > —style <path-to-style> <path-to-file>" > > Dropping the —style, I can verify that this command does indeed drop > revisions on other branches. The problem seems to be the —follow option. It > does not only track file renames, but also restricts output to > ancestors/descendants of the starting revision, which defaults to the > current revision. > > To track renames while also showing the file history across different > branches, one needs to explicitly specify a revision range that can reach > other branches ( i.e. —rev ':' ). > > This works, but is a HUGE slowdown. In the hg command line, hg log > <path-to-file> is near instant, while hg log -f <path-to-file> -r : takes > upwards of 10 seconds. > > I am now sure how I can use the defaults setting to override the > behaviour, since —follow is explicitly part of the command. Could we get a > preference option to enable/disable —follow? > > Kind regards, > Paul > > -- You received this message because you are subscribed to the Google Groups "MercurialEclipse" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
