From: Stefan Beller Date: Thu, 22 Jan 2015 23:11:32 GMT Subject: [RFC PATCH 0/5] So you dislike the sequence of system calls? Message-ID: <1421968297-25407-1-git-send-email-sbeller@google.com> In-Reply-To: <54C0DDE7.8030708@alum.mit.edu> This series goes on top of origin/sb/atomic-push-fix for now. I am inclined to squash the first patch into the last commit of origin/sb/atomic-push-fix when rerolling that series as it just fixes the warning Ramsay pointed out. I'd also like to combine this series with the origin/sb/atomic-push-fix in a reroll of either series such that it becomes one larger series. The patches 2,3,4 are just preparations (no change intended) for the patch 5 which then corrects the sequence of system calls such that we don't close and reopen the lock file. (Background: Why am I spending time to fix that bug the way I do?) I think writing out the sha1 early to the .lock file helps in further patch series for cross repository atomic pushes, because if we can split the transaction_commit into two parts, where the latter part only has lock file pathes in memory, dealing with cross repository ref updates becomes easy in such a way: (compare discussion [RFC] Introducing different handling for small/large transactions) cat << EOF > stdin_pipe delete topic2 2345 update master 4567 2378 repository ../API-consumer # this switches to another repository delete topic2 3459 update master 6787 9878 EOF git update-ref --stdin