git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 2/2] Mention "git blame" improvements in release notes

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 26, 2014, 17:28 UTC
Message-ID
<7vmwf8huey.fsf@alter.siamese.dyndns.org>
In-Reply-To
<1398470210-28746-2-git-send-email-dak@gnu.org>
David Kastrup <dak@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 later.

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 mentioning it.

Thanks for working on the topic.
Show 22 quoted lines
>
> Signed-off-by: David Kastrup <dak@gnu.org>
> ---
>  Documentation/RelNotes/2.0.0.txt | 6 ++++++
>  1 file changed, 6 insertions(+)
>
> diff --git a/Documentation/RelNotes/2.0.0.txt b/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 <dak@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
>     updated.
Previous: David KastrupNext: David Kastrup
Message 3 of 20 in “blame: large-scale performance rewrite”
  1. 1/2 blame: large-scale performance rewriteDavid Kastrup, Apr 25, 2014
  2. 2/2 Mention "git blame" improvements in release notesDavid Kastrup, Apr 25, 2014
  3. Junio C HamanoApr 26, 2014
  4. David KastrupApr 26, 2014
  5. Shawn PearceApr 26, 2014
  6. David KastrupApr 26, 2014
  7. Shawn PearceApr 26, 2014
  8. David KastrupApr 26, 2014
  9. Shawn PearceApr 26, 2014
  10. David KastrupApr 26, 2014
  11. David KastrupApr 26, 2014
  12. David KastrupApr 26, 2014
  13. Shawn PearceApr 26, 2014
  14. David KastrupApr 26, 2014
  15. Shawn PearceApr 27, 2014
  16. David KastrupApr 28, 2014
  17. Junio C HamanoApr 28, 2014
  18. David KastrupApr 28, 2014
  19. Ronnie SahlbergApr 28, 2014
  20. David KastrupApr 28, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.