version2: * This applies on top of origin/sb/atomic-push though it will result in a one line merge conflict with origin/jk/lock-ref-sha1-basic-return-errors when merging to origin/next. * It now uses the FILE* pointer instead of file descriptors. This results in a combination of the 2 former patches "refs.c: have a write_in_full_to_lock_file wrapper" and "refs.c: write to a lock file only once" as the wrapper function is more adapted to its consumers * no need to dance around with char *pointers which may leak. * another new patch sneaked into the series: Renaming ULIMIT in t7004 to ULIMIT_STACK_SIZE That said, only the first and third patch are updated from the first version of the patches. The others are new in the sense that rewriting them was cheaper than keeping notes in between. version1: (reported as: git update-ref --stdin : too many open files, 2014-12-20) First a test case is introduced to demonstrate the failure, the patches 2-6 are little refactoring and the last patch fixes the bug and also marks the bugs as resolved in the test suite. Unfortunately this applies on top of origin/next. Any feedback would be welcome! Thanks, Stefan Stefan Beller (5): 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: have a write_sha1_to_lock_file wrapper refs.c: enable large transactions refs.c | 34 ++++++++++++++++++++++------------ t/t1400-update-ref.sh | 28 ++++++++++++++++++++++++++++ t/t7004-tag.sh | 4 ++-- 3 files changed, 52 insertions(+), 14 deletions(-) -- 2.2.1.62.g3f15098 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
