[zokier]

What pijul needs to truly succeed is an halo project. Git got where it is now only because it was developed for linux kernel. Not only is it a major pr boost, but it also gets all sorts of kinks ironed out pretty quickly, and that the tool fits into different peoples workflows; for linux that means that git format-patch and am were pretty much day1 features so that it works with lkml flow seamlessly.

rustc could be one strong candidate as such halo project, but it is probably pretty difficult to convince them to switch, especially as it means not only switching away from git, but also github which they use heavily.

Which conveniently brings to last point that to get any major project to switch to pijul, the transition story needs to be really solid and not disruptive to the day-to-day development. For git it meant not only that it needed to work well with lkml, but git also had really solid svn and cvs (and others!) clients pretty early on. It allowed people to use both git and the legacy vcs in parallel during transition. Beyond that, individuals could use git to work with svn (and other vcs) repos that had no plans to transition anywhere, and still reap some of gits benefits.

For pijul I think it means that it is necessary to be able to work with git repos seamlessly similarly that git-svn allowed git users to work with svn repos.