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

Re: What's cooking in git.git (Jul 2016, #05; Wed, 13)

From
Stefan Beller <sbeller@google.com>
Date
Jul 13, 2016, 17:52 UTC
Message-ID
<CAGZ79kYUMX7wewo2QEWQGU9sGR76XjrKJ3uJxpLnyWoZeZ6WXA@mail.gmail.com>
In-Reply-To
<xmqqpoqh1m0o.fsf@gitster.mtv.corp.google.com>
On Wed, Jul 13, 2016 at 10:32 AM, Junio C Hamano <gitster@pobox.com> wrote:
Show 9 quoted lines
> Stefan Beller <sbeller@google.com> writes:
>
>>> * sb/push-options (2016-07-12) 5 commits
>>>  - add a test for push options
>>>  - push: accept push options
>>>  - SQUASH???
>>
>> Squash? I do not find a squashable commit in what you pushed,
>> do you intend to squash the first 2 patches instead?

Oh I pulled a few minutes before you sent this email, and forgot that you likely have pushed again when sending this email. :/ Thanks!

Show 7 quoted lines
>> Yeah there were some late comments, so I did not reroll right away.
>> I think Shawns proposal to have a receive.maxCommandBytes is a
>> good way for an overall upper bound, but how does it stop us from
>> going forward with this series?
>
> If we were to do maxcommandbytes, then max_options would become
> irrelevant, no?
Maybe?

I do not know what kind of safety measures we want in place here, and if we want to go for overlapping things?

Currently there are none at all in your upstream code, although you cannot push arbitrary large things to either Shawns or Peffs $Dayjob servers, so I wonder if we want to either agree on one format or on many overlapping things, as some different hosts may perceive different things as DoS threats, so they can fine tune as they want?

In the Gerrit world, you have a ref per code review, such that it is easy to have 50k refs or more, similar to the repo Jeff pointed out [1], that has 40k tags (and getting a new tag every 2 hours apparently).

So I could understand if different services care about the different loads (refs vs push options) differently (one would want to allow unlimited refs pushing for mirroring such repos as pointed out above, while another one might care about the total load of the server for a single rogue user)

Thanks, Stefan

[1] https://github.com/JetBrains/intellij-community
Previous: Junio C HamanoNext: Junio C Hamano
Message 4 of 21 in “What's cooking in git.git (Jul 2016, #05; Wed, 13)”
  1. Junio C HamanoJul 13, 2016
  2. Stefan BellerJul 13, 2016
  3. Junio C HamanoJul 13, 2016
  4. Stefan BellerJul 13, 2016
  5. Junio C HamanoJul 13, 2016
  6. Junio C HamanoJul 13, 2016
  7. Jeff KingJul 13, 2016
  8. Duy NguyenJul 13, 2016
  9. Junio C HamanoJul 13, 2016
  10. Johannes SchindelinJul 14, 2016
  11. Johannes SchindelinJul 14, 2016
  12. Junio C HamanoJul 14, 2016
  13. Johannes SchindelinJul 14, 2016
  14. Junio C HamanoJul 14, 2016
  15. Lars SchneiderJul 16, 2016
  16. Eric WongJul 16, 2016
  17. Lars SchneiderJul 16, 2016
  18. list: avoid incompatibility with *BSD sys/queue.hEric Wong, Jul 17, 2016
  19. Eric SunshineJul 17, 2016
  20. Eric WongJul 17, 2016
  21. Lars SchneiderJul 18, 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.