From: David Kastrup <dak@gnu.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/2] Mention "git blame" improvements in release notes
Date: Mon, 28 Apr 2014 21:57:19 +0200 [thread overview]
Message-ID: <87ha5d4480.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <xmqq38gxqmc9.fsf@gitster.dls.corp.google.com> (Junio C. Hamano's message of "Mon, 28 Apr 2014 12:35:02 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> I guess we probably can add "See $URL if you are interested in his
> further plans" after that two-line item and let you write whatever
> you want at that page pointed at by the URL, though.
I most definitely am _not_ planning to invest any more time into Git
since even designing such plans would be throwing good time after bad
time. And I don't have a web presence anyway. As it does not appear
that there is any realistic manner in which Git users could even be made
aware of a connection between monetary requirements and work for a
freelancer like myself, I'll be just writing this off as a one-time
mistake on my part given my personal situation. It's not the first, and
it will certainly not be the last, but at least I can avoid doing the
same mistake twice on the same project.
There are some low-hanging fruit for further speeding up git-blame now
that its internal thrashing has been addressed. I will point out those
low-hanging fruit so that anybody can follow up on it and do all the
arguing and benchmarking required to go anywhere and get the credit for
it.
But that's as far as my willingness to "do the right thing" will carry.
If nobody picks up either the tab or the rather simple followup tasks,
then that's what the community and customer base of Git is capable of
sustaining and I'm not in a position to change it.
--
David Kastrup
next prev parent reply other threads:[~2014-04-28 19:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-25 23:56 [PATCH 1/2] blame: large-scale performance rewrite David Kastrup
2014-04-25 23:56 ` [PATCH 2/2] Mention "git blame" improvements in release notes David Kastrup
2014-04-26 17:28 ` Junio C Hamano
2014-04-26 18:28 ` David Kastrup
[not found] ` <xmqqzjj5s8hs.fsf@gitster.dls.corp.google.com>
2014-04-28 17:39 ` David Kastrup
2014-04-28 19:35 ` Junio C Hamano
2014-04-28 19:57 ` David Kastrup [this message]
2014-04-28 20:05 ` Ronnie Sahlberg
2014-04-28 20:26 ` David Kastrup
2014-04-26 0:53 ` [PATCH 1/2] blame: large-scale performance rewrite Shawn Pearce
2014-04-26 7:48 ` David Kastrup
2014-04-26 16:01 ` Shawn Pearce
2014-04-26 16:50 ` David Kastrup
2014-04-26 17:09 ` Shawn Pearce
2014-04-26 17:22 ` David Kastrup
2014-04-26 17:02 ` David Kastrup
2014-04-26 17:30 ` David Kastrup
2014-04-26 17:56 ` Shawn Pearce
2014-04-26 21:39 ` David Kastrup
2014-04-27 17:53 ` Shawn Pearce
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=87ha5d4480.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).