git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Make "git checkout" automatically update submodules?

From
KGKannan Goundan <kannan@cakoose.com>
Date
Oct 23, 2015, 03:46 UTC
Message-ID
<loom.20151023T044009-172@post.gmane.org>
In-Reply-To
<xmqq37x2qqzf.fsf@gitster.mtv.corp.google.com>
Junio C Hamano <gitster <at> pobox.com> writes:
Show 7 quoted lines
> We are unfortunately not set up to handle money well.  For a
> background explanation, please go read [*1*], which I wrote my take
> on "money" some time ago.  Note that it is an explanation and not a
> justification.  It explains why we are not set up to handle money
> well and what the issues around money that are troublesome for the
> project are.  It does not mean to say that it is a good thing that
> it is hard to buy feature with money from our project [*2*].

I think the way I described it ("sponsoring a feature") doesn't really reflect how I was imagining it. In my head, it looked like this:

1. Figure out whether the Git community and maintainers seem ok with the
overall feature idea.  If not, give up.
2. Come up with a plan for the UI/UX; see if the Git community and
maintainers seem ok with it.  If not, iterate or give up.
3. Implement it, then go through the regular process of getting it merged
upstream.  If it doesn't go well, might have to iterate or give up.

I could try doing that myself, but someone familiar with the Git codebase/community/history would be better at it (and probably be easier for you guys to work with :-)

I guess I'm just wondering if there are people who meet those qualifications and are interested in going through those steps for pay. Or maybe there's a company that does this, like the old Cygnus Solutions?

In particular, I don't expect anything to change about the project's development process.

(This part is not relevant to the Git project, but I understand that it's hard for anyone to guarantee a feature will make it into an open source project. I imagine these kinds of contracts are set up so that you're primarily paying for the effort, not the outcome. If it ends up not working out, you don't get your money back.)

Previous: Junio C HamanoNext: Christian Couder
Message 5 of 10 in “Make "git checkout" automatically update submodules?”
  1. Kannan GoundanOct 15, 2015
  2. Junio C HamanoOct 15, 2015
  3. Kannan GoundanOct 22, 2015
  4. Junio C HamanoOct 23, 2015
  5. Kannan GoundanOct 23, 2015
  6. Christian CouderOct 23, 2015
  7. Junio C HamanoOct 23, 2015
  8. Stefan BellerOct 23, 2015
  9. Junio C HamanoOct 23, 2015
  10. Kannan GoundanOct 23, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.