On November 4, 2016 7:48:17 PM MDT, Jeff King <peff@xxxxxxxx> wrote: >On Fri, Nov 04, 2016 at 04:34:34PM -0700, Jacob Keller wrote: > >> > You might also want fallback rules for storing gitrefs on "old" >servers >> > (e.g., backfilling gitrefs you need if the server didn't them in >the >> > initial fetch). But I guess storing any gitrefs on such a server is >> > inherently dangerous, because the server might prune them at any >time. >> >> Is it possible currently for a protocol extension to result in "oh >the >> server doesn't support this so I'm going to stop pushing"? > >Yes, it would be easy for the client to abort if the server fails to >advertise a particular extension. And the reverse (old client, new server) should work as well? - Josh Triplett