Michael Haggerty <mhagger@xxxxxxxxxxxx> writes: > Now that 1.7.8 is out, I wanted to figure out the status of the > remaining ref-api changes that are in flight, including the differences > between between my tree and yours. I understand that the ultimate and largest objective of these series is to make sure that the performance does not suffer from very many negative lookups on the refs/replace hierarchy (which almost always is empty in a sane repository), and I do want to see that happen. I also think it is good that the series tries to make sure that the various codepaths we create new refs do not let the user accidentally create refs with bad names and/or contents. When we see a questionable ref that is _already_ in the respository, however, we may warn but it is wrong to declare the repository to be broken and refuse to work. That would make it cumbersome or impossible to even _fix_ such breakage. Regressions of that kind wer in the earlier part of the series already in 1.7.8 and it was rather unpleasant having to hotfix them. As our test suite does not deliberately create these questionable refs and/or try to use them (and I personally do not in my regular workflow either), I am afraid that it is rather hard to realize what kind of refnames are what we intended to forbid even from earlier days but did not _bother_ to check and enforce the rule against so far, but are forbidden by the updated code, until we unleash the new logic to the end users with various third party tools that created them [*1*]. I would want to see us get this part right and solid, and include it in 1.7.9. It would be nice if we can include also the bits to read hierarchies lazily, but as they come on top of your B & C, it may end up in 1.7.10 and I do not mind it at all. Reference resolution is one of the central things in the user experience, and we cannot afford to ship anything that is half-done-and-mostly-works over slow-but-correct. Alternatively you _could_ swap the order of your B & C and D and try to have your D early while giving B & C more time to cook, but I suspect the order you chose would be better in the longer term. > I understand that "next" will soon be re-rolled. Will the re-roll be > based on the current "pu", or will you start from scratch? As to the two quickfix patches that are on two remaining topics from you in my tree, I did them merely as a short-term band-aid. I was expecting, after 1.7.8 when we eject the topics out of 'next', that they will be rebased on top of 'master' that already contains a proper fix before these topics started touching the same codepath. My reading of your summary suggests that it would be easiest to drop the three mh/ref-api* topics from my tree, especially the 'refs: loosen over-strict "format" check' band-aid patches, and re-queue a re-roll from you. Thanks. [Footnote] *1* Trying to be lenient when reading and being strict when writing as the general principle would be the safe and sane way forward, and making sure that we warn *loudly* when we think we are merely being lenient (i.e. we think we found a bad ref with questionable name and/or contents) would be a good way to catch our mistakes early. E.g. ".git/config does not record a correct object name" glitch was caught only because you added the warning so while it was painful to hotfix that late in the cycle, the warning was worth it. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html