On Fri, Feb 24, 2017 at 5:00 PM, David Lang <da...@lang.hm> wrote: > On Fri, 24 Feb 2017, Jeff King wrote: > >> >> So I'd much rather see strong rules like: >> >> 1. Once a repo has flag-day switched over to the new hash format[1], >> new references are _always_ done with the new hash. Even ones that >> point to pre-flag-day objects! > > > how do you define when a repo has "switched over" to the new format in a > distributed environment? > > so you have one person working on a project that switches their version of > git to the new one that uses the new format. > > But other people they interact with still use older versions of git > > what happens when you have someone working on two different projects where > one has switched and the other hasn't?
you get infected by the "new version requirement" as soon as you pull? (GPL is cancer, anyone? ;) If you are using an old version of git that doesn't understand the new version, you're screwed.
