On Fri, Nov 4, 2016 at 2:55 PM, Josh Triplett <josh@xxxxxxxxxxxxxxxx> wrote: > That said, I'd *love* to have gitrefs available, for a wide variety of > applications, and I can see an argument for introducing them and waiting > a few years for them to become universally available, similar to the > process gitlinks went through. > > But I'd also love to have a backward-compatible solution. > > - Josh Triplett I think that you won't really find a backwards compatible solution other than something like automatically generating refs for each point of history. I know that gerrit does something like this by storing each version in "refs/changes/id/version" or something along those lines. I think this might actually be cleaner than your parent links hack, and could be used as a fallback for when gitrefs don't work, though you'd have to code exactly how to tell what to push to a repository when pushing a series? Thanks, Jake