From: Alex <ajb44.geo@yahoo.com>
To: git@vger.kernel.org
Subject: Re: Implicit stashes
Date: Wed, 30 Jun 2010 11:27:30 +0000 (UTC) [thread overview]
Message-ID: <loom.20100630T132533-495@post.gmane.org> (raw)
In-Reply-To: AANLkTimIJcOe3fufZx83LxI8ZSDP8cCOj1BEPPbUy7Ol@mail.gmail.com
Sverre Rabbelier <srabbelier <at> gmail.com> writes:
> Hehe, I'll match your $50 and raise you a beer ;). Isn't there some
> relevant site where people can pledge for stuff like this? Either way,
> I doubt for most lack of financial stimulation is what's stopping them
> from implementing this, but rather lack of time which cannot really be
> compensated financially.
There are a few:
http://fossfactory.org
http://nextsprocket.com
http://www.opensourcexperts.com/
Alex
next prev parent reply other threads:[~2010-06-30 11:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-30 2:48 Implicit stashes John Tapsell
2010-06-30 2:56 ` Joshua Jensen
2010-06-30 3:05 ` John Tapsell
2010-06-30 5:57 ` Sverre Rabbelier
2010-06-30 11:27 ` Alex [this message]
2010-06-30 5:13 ` Dangers of reset --hard (Re: Implicit stashes) Jonathan Nieder
2010-06-30 8:19 ` Will Palmer
2010-06-30 16:12 ` Jonathan Nieder
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=loom.20100630T132533-495@post.gmane.org \
--to=ajb44.geo@yahoo.com \
--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 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).