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

[PATCH 0/3] Large transactions in git

From
Stefan Beller <sbeller@google.com>
Date
Apr 14, 2015, 22:25 UTC
Message-ID
<1429050308-9617-1-git-send-email-sbeller@google.com>

On Git Merge Wilhelm Bierbaum from Twitter made clear that we'd have problems with large transactions in git. As I have been working on that series a few months ago and it still bugs me, I thought about reviving the series.

However the series got stale a few months ago because we were not sure how to do it right. The first few patches were deemed uncontroversial though, which I am resending now.

The first patch contains tests telling us what needs fixing. The second patch renames the precondition for other tests, as ULIMIT is a bit generic. The third patch removes the `lock_fd` field from struct ref_lock which was duplicate information.

That said, this series is not fixing the actual issue, but I'd guess having these patches is step forward actually.

Thanks, Stefan

Stefan Beller (3):
  update-ref: test handling large transactions properly
  t7004: rename ULIMIT test prerequisite to ULIMIT_STACK_SIZE
  refs.c: remove lock_fd from struct ref_lock
 refs.c                | 16 ++++++----------
 t/t1400-update-ref.sh | 28 ++++++++++++++++++++++++++++
 t/t7004-tag.sh        |  4 ++--
 3 files changed, 36 insertions(+), 12 deletions(-)
-- 
2.3.0.81.gc37f363
Next: Stefan Beller
Message 1 of 7 in “Large transactions in git”
  1. 0/3 Large transactions in gitStefan Beller, Apr 14, 2015
  2. 1/3 update-ref: test handling large transactions properlyStefan Beller, Apr 14, 2015
  3. 2/3 t7004: rename ULIMIT test prerequisite to ULIMIT_STACK_SIZEStefan Beller, Apr 14, 2015
  4. 3/3 refs.c: remove lock_fd from struct ref_lockStefan Beller, Apr 14, 2015
  5. Junio C HamanoApr 14, 2015
  6. Michael HaggertyApr 15, 2015
  7. Junio C HamanoApr 15, 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.