From: David Kastrup <dak@gnu.org>
To: Ronnie Sahlberg <sahlberg@google.com>
Cc: Junio C Hamano <gitster@pobox.com>,
"git\@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [PATCH 2/2] Mention "git blame" improvements in release notes
Date: Mon, 28 Apr 2014 22:26:45 +0200 [thread overview]
Message-ID: <87d2g142uy.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <CAL=YDW=iTQz-S+ZByZnVhrpebPgZxq6p46MC2yqW-HF3eVw+2g@mail.gmail.com> (Ronnie Sahlberg's message of "Mon, 28 Apr 2014 13:05:28 -0700")
Ronnie Sahlberg <sahlberg@google.com> writes:
> Some projects, for example samba, provide a dedicated page on the
> project web site
> where vendors, and I think individuals, that provide services can list
> their information :
>
> http://www.samba.org/samba/support/
>
> Would this perhaps be a better solution?
Actually, it does not work for my situation at all but then my situation
is likely not typical enough to be worth catering for specifically.
The salient point with me is that my productivity drops by more than a
factor of 100 (no, that's not an exaggeration) when having to do
something I'm not interested in.
Which is the reason my deal with GNU LilyPond where I'm (interrupted by
the git-blame episode) basically lead programmer is that LilyPond users
give me whatever money they consider my work to be worth to them, and in
return I work on whatever I like on LilyPond. Nobody gets to say _what_
I do, and that's to the best of everyone's interest since only that way
a reasonable amount of work actually gets done.
So I cannot actually provide "services for hire" but it's more like a
"themed money sink" I can offer. And in the case of Git, since it does
not even appear that there is a continuing base to make it work
reasonably in the context of other contributors and their interests,
it's more like "oops, I ended up wasting months on your project, but at
least there was something to show for it from my side, how about
yours?". That's not something one can reasonably put on a "support"
themed page. It's actually bloody ridiculous but then that's the sort
of handicap I have to organize my life around. Even while it's
unpredictable what I end up doing, once I do get something done it tends
to be pretty good (there are a few old performance patches of mine in
the Git code base where I did not start out from what happens to be
pretty awful code and still got considerable return).
--
David Kastrup
next prev parent reply other threads:[~2014-04-28 20:26 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
2014-04-28 20:05 ` Ronnie Sahlberg
2014-04-28 20:26 ` David Kastrup [this message]
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=87d2g142uy.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sahlberg@google.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).