On Jul 16, 2012 1:18 PM, "Branko Čibej" <br...@wandisco.com> wrote: >... > Please describe the set of use cases you want to address, propose how > you think this new property can solve them, and at the very least, > explain how the solution will affect: a) the command-line client, b) > every other client, c) branching and merging, d) sparse checkouts, e) > externals. And explore other usage models than the one you have in mind > and think about how the proposed change will affect them.
I want to make a community meta-comment here: It is fair to say "it won't work because $foo." It is not fair to say "before scratching your itch, you must satisfy *my* half-dozen requirements." We contribute on our own time, but those contributions cannot be gated by others a priori. We ask for discussion and consensus before large conceptual changes, but there are many ways to get to a rough consensus before implementation begins. And that doesn't usually require a whitepaper. Cheers, -g
