"Sean Barag via GitGitGadget" <gitgitgadget@xxxxxxxxx> writes: > Took another pass at supporting a configurable default for-o/--origin, this > time following Junio's suggestions from a previous approach as much as > possible [1]. Unfortunately, Johannes mentioned that --template can write > new config values that aren't automatically merged without re-calling > git_config. There doesn't appear to be a way around this without rewriting > significant amounts of init and config logic across the codebase. > > While this could have been v2 of the original patchset, it's diverged so > drastically from the original that it likely warrants its own root thread. > If that's not appropriate though, I'd be happy to restructure! I did wonder if this series came from the same motivation while scanning messages in the mailbox and saw no "v2" in the subject, but I am OK either way in a case like this. I DO appreciate this note to explain why it is not marked with "v2".
