Re: [PATCH v3 00/13] ci: include a Visual Studio build & test in our Azure Pipeline

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Dscho,
On 10/10/2019 10:03, Johannes Schindelin wrote:
So a better interpretation would have been:

  The default creation factor is 60 (roughly speaking, it wants at
  most 60% of the diffs' lines to differ, otherwise it considers
  them not to be a match.

This is still inaccurate, but at least it gets the idea of the
range-diff across.

Of course, I will never be able to amend the commit message in
GitGitGadget anyway, as I have merged that PR already.

Ciao,
Dscho
Medium term, is this something that could go in the algorithms section of the
range-diff man page, especially if the upstream commit message is already in
place.

#leftoverdocs ?
Sure. How about giving it a try while our memory is still fresh? You
would help me immensely if you could take that task off of my plate...
My sneak think was to introduce the new hash tag for useful explanations from the list that could be copied into the man/guide pages, especially for the project pages.

At the moment I'm trying to get the >4Gb on Window' series sorted, which though working has been a load of bear traps for testing and configs and VS compiling, etc.
But yes, it is on the back-list.
--
Philip



[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux