Han-Wen Nienhuys <hanwen@xxxxxxxxxx> writes: > Sounds great to me. Could we submit a patch that changes this into > master already so Brian and can work on the same basis? Heh, "into master already" is never be the way things work around here. But if these two topics can agree the best way forward, it can be proposed, polished and then merged to 'master', just like any other topic. And the two topics both can build on top of that topic. >> I am not sure how quickly Brian's SHA-256 work solidifies enough to >> build on top of, but if it is a good option to build on top of the >> topic, that may save some work from this topic, too, as the >> mechanism to choose something (i.e. hash algorithm for Brian's >> topic, ref backend for this topic) fundamental to the repository at >> runtime and at initialization time needs similar supporting >> infrastructure, such as changes in "[12/24] setup: allow >> check_repository_format to read repository format", and "[13/24] >> builtin/init-db: allow specifying hash algorithm on command line" >> of that series. > > Can I pull this series as a git branch somewhere? There is a single merge somewhere on "git log --first-parent master..pu" that merges bc/sha-256- something (I assume you know how to obtain 'pu'). Thanks.
