From: Junio C Hamano <gitster@pobox.com>
To: David Kastrup <dak@gnu.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/2] Mention "git blame" improvements in release notes
Date: Mon, 28 Apr 2014 12:35:02 -0700 [thread overview]
Message-ID: <xmqq38gxqmc9.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <87y4yp4ame.fsf@fencepost.gnu.org> (David Kastrup's message of "Mon, 28 Apr 2014 19:39:05 +0200")
David Kastrup <dak@gnu.org> writes:
> Junio C Hamano <gitster@pobox.com> writes:
>
>> But still, I am not convinced that the release notes is a good place
>> to do this, and would be happier if you can think of a better venue.
>
> "This change has been contributed by an independent developer on a
> contingency base. To make this approach work, please contact him if you
> consider it worth recompensating."
I write things under three personalities. As just one of the people
active in the Git development community, as the maintainer of the
project, and saying things on behalf of "the Git project".
The distinction between the latter two may be subtle, but it matters
to me. And in my mind, I write the Release Notes on behalf of the
project.
* The performance of "git blame" has been greatly improved. Thanks
David Kastrup for his huge effort.
is perhaps as far as I can go in that capacity, without singling out
one contributor among 80+ contributors with changes between 1.9 and
2.0 (among which a dozen or so have more than 10 patches---some are
trivial and patch count alone does not do justice, though) with
similar "pay them to show your appreciation" pleas.
I however feel that I can certainly do that as an active (and highly
visible) contributor, and even as the maintainer.
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.
next prev parent reply other threads:[~2014-04-28 19:35 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 [this message]
2014-04-28 19:57 ` David Kastrup
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=xmqq38gxqmc9.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=dak@gnu.org \
--cc=git@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.