David Kastrup <d...@gnu.org> writes:
> Includes reasonably tasteful begging.
Thanks, but no thanks---I do not see it tasteful.
In any case, any large change that is not a regression fix (or a fix
to a code added since 1.9 series) is way too late for 2.0 at this
point, but I do look forward to reading the patch over, queuing to
my tree, cooking in 'next' and eventually having this in 2.1 or
If you want help in a fundraising campaign, I can lend my name
(especially after this change settles and proves to be useful ;-),
but let's do that elsewhere. I do not want to do this in the release
notes (e.g., an entry in git-blame blog can mention it when it
touches the blame improvements).
This by the way touches another thing I have been wondering.
Perhaps I should stop having the top-level RelNotes as a symbolic
link, but keep it as a regular file, which I *copy* to its current
location in the commit that tags the release. And then I start a
skeletal RelNotes at the top of the tree when the next cycle begins,
and new topics will build on top of that commit.
That way, this patch would have been against the top-level RelNotes,
applied as part of the topic, and when the topic is merged to
'master', it would make it less likely for me to forget about
Thanks for working on the topic.
> Signed-off-by: David Kastrup <d...@gnu.org>
> Documentation/RelNotes/2.0.0.txt | 6 ++++++
> 1 file changed, 6 insertions(+)
> diff --git a/Documentation/RelNotes/2.0.0.txt
> index ffd4899..27b23c3 100644
> --- a/Documentation/RelNotes/2.0.0.txt
> +++ b/Documentation/RelNotes/2.0.0.txt
> @@ -144,6 +144,12 @@ UI, Workflows & Features
> Performance, Internal Implementation, etc.
> + * Significant parts of "git blame" have been reimplemented by David
> + Kastrup <d...@gnu.org> for a vast gain in performance with complex
> + histories and large files. As working on free software is his sole
> + source of income, please consider contributing to his remuneration
> + if you find this useful.
> * The compilation options to port to AIX and to MSVC have been
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html