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

Re: [PATCH/RFC/GSoC 0/2] add a add.patch config variable

From
DFDominik Fischer <d.f.fischer@web.de>
Date
Apr 21, 2016, 17:28 UTC
Message-ID
<d6747d29-601f-d9ba-2f27-812bf064edff@web.de>
In-Reply-To
<xmqq4mauucx6.fsf@gitster.mtv.corp.google.com>
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:
 > any transition plan would be far more painful than the possible benefits
I agree, it cannot be expected that every external script sets 
GIT_RECURSION_DEPTH before issuing any command just because of this 
little option.

As an exercise for GSoC, I implemented it nonetheless to get more familiar with the code base and testing system and receive some feedback. Perhaps the counter can even be useful for some actually significant use case in the future.

Regards.
Previous: Junio C HamanoNext: Johannes Schindelin
Message 8 of 10 in “add a add.patch config variable”
  1. 0/2 add a add.patch config variableXZS, Apr 21, 2016
  2. 1/2 count recursion depthXZS, Apr 21, 2016
  3. 2/2 add a add.patch config variableXZS, Apr 21, 2016
  4. Johannes SchindelinApr 21, 2016
  5. Dominik FischerApr 21, 2016
  6. Matthieu MoyApr 21, 2016
  7. Junio C HamanoApr 21, 2016
  8. Dominik FischerApr 21, 2016
  9. Johannes SchindelinApr 22, 2016
  10. Johannes SchindelinApr 22, 2016

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.