From: 井上司 Date: Tue, 20 Oct 2026 06:33:51 GMT Subject: Re: switch/checkout stops halfway when it fails to write tracking config Message-ID: In-Reply-To: Thanks for the reply. I agree with your point. However, implementing full atomicity now would be a large change, for two reasons: - push -u, clone and fetch continue even when writing the tracking config fails, but setup_tracking() calls exit() and aborts the process. - For full atomicity, we would need to undo the worktree, the ref and the config. We would also need to handle the die() calls in checkout. So I propose to make setup_tracking() return an error instead of calling exit(), so that switch and checkout can behave like the other callers, and to leave full atomicity as a separate topic. 2026年10月20日(火) 13:11 Junio C Hamano : > > 井上司 writes: > > > 7. Next steps > > I would like to work on a fix. Should checkout finish the switch and only > > report the tracking error, or should it fail before touching the worktree? > > Either would be an improvement over the reported behaviour, but if > we can make it atomic "all-or-none" matter, that would be more > preferrable than switching without setting up the tracking.