From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Dave Borowitz <dborowitz@google.com>, git <git@vger.kernel.org>
Subject: Re: Git + SFC Status Update
Date: Wed, 15 Apr 2015 01:54:26 +0200 [thread overview]
Message-ID: <20150414235425.GA2179@peff.net> (raw)
In-Reply-To: <xmqq7fte33u8.fsf@gitster.dls.corp.google.com>
On Tue, Apr 14, 2015 at 12:30:23PM -0700, Junio C Hamano wrote:
> > If I recall correctly, Scott said onstage that some/all of the
> > conference proceeds would be going directly into this fund. So this
> > might need to be revised upward by 50-100% sometime soon :)
>
> I think you misheard it. The above is money earmarked for Git at
> SFC; the admission for GitMerge were going to SFC general fund
> without earmarked for us, IIUC.
Yeah, that's my understanding as well.
-Peff
next prev parent reply other threads:[~2015-04-14 23:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-13 11:56 Git + SFC Status Update Jeff King
2015-04-13 15:24 ` Michael J Gruber
2015-04-14 19:00 ` Dave Borowitz
2015-04-14 19:30 ` Junio C Hamano
2015-04-14 23:54 ` Jeff King [this message]
2015-04-15 15:55 ` Dave Borowitz
2015-04-15 16:07 ` Junio C Hamano
2015-04-16 8:37 ` Yi EungJun
2015-04-16 9:31 ` Jeff King
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=20150414235425.GA2179@peff.net \
--to=peff@peff.net \
--cc=dborowitz@google.com \
--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).