From: Christian Couder <christian.couder@gmail.com>
To: David Kastrup <dak@gnu.org>
Cc: git <git@vger.kernel.org>, Junio C Hamano <gitster@pobox.com>,
Eric Sunshine <sunshine@sunshineco.com>,
Matthieu Moy <Matthieu.Moy@imag.fr>,
Nguyen Thai Ngoc Duy <pclouds@gmail.com>,
Paul Tan <pyokagan@gmail.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Dongcan Jiang <dongcan.jiang@gmail.com>,
Jeff King <peff@peff.net>, Doug Kelly <dougk.ff7@gmail.com>,
Bharat Suvarna <bharat.bs84@icloud.com>, Kevin D <me@ikke.info>,
"Randall S. Becker" <rsbecker@nexbridge.com>,
Stephen Robin <stephen.robin@gmail.com>,
Thomas Ferris Nicolaisen <tfnico@gmail.com>
Subject: Re: Draft of Git Rev News edition 1
Date: Sun, 22 Mar 2015 13:19:13 +0100 [thread overview]
Message-ID: <CAP8UFD1HFVKr1xADSGDzJGXeve7W9eenpL16kRa_2z2rsJU_GA@mail.gmail.com> (raw)
In-Reply-To: <87lhipnupj.fsf@fencepost.gnu.org>
On Sun, Mar 22, 2015 at 12:21 PM, David Kastrup <dak@gnu.org> wrote:
> I've seen
>
> David Kastrup (dak at gnu.org) previously reimplemented significant
> parts of "git blame" 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 kind of improvements useful.
>
> Thank you very much for this heads-up. However, I'd replace
> "previously" with "as of version 2.1.0". That's where the big
> difference is, so if people actually are impacted they'll know whether
> and what to benchmark and/or upgrade.
Ok, there is now "as of version 2.1.0".
next prev parent reply other threads:[~2015-03-22 12:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-22 11:03 Draft of Git Rev News edition 1 Christian Couder
2015-03-22 11:21 ` David Kastrup
2015-03-22 12:19 ` Christian Couder [this message]
2015-03-22 20:52 ` Thomas Ferris Nicolaisen
2015-03-22 21:24 ` David Kastrup
2015-03-22 18:47 ` Junio C Hamano
2015-03-22 20:50 ` Thomas Ferris Nicolaisen
2015-03-23 4:49 ` Junio C Hamano
2015-03-23 5:00 ` Christian Couder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAP8UFD1HFVKr1xADSGDzJGXeve7W9eenpL16kRa_2z2rsJU_GA@mail.gmail.com \
--to=christian.couder@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=Matthieu.Moy@imag.fr \
--cc=bharat.bs84@icloud.com \
--cc=dak@gnu.org \
--cc=dongcan.jiang@gmail.com \
--cc=dougk.ff7@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=me@ikke.info \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
--cc=pyokagan@gmail.com \
--cc=rsbecker@nexbridge.com \
--cc=stephen.robin@gmail.com \
--cc=sunshine@sunshineco.com \
--cc=tfnico@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).