Re: [RFC 0/1] Tolerate broken headers in `packed-refs` files

From: Edward Thomson <ethomson@edwardthomson.com>
Date: Mar 26, 2018, 14:33 UTC
Message-ID: <CA+WKDT1LMuwuXar9i-1RJ15+o5Rxp013FL9fqfAfMydZJ9cQ6g@mail.gmail.com>
In-Reply-To: <f8d0f3b6-69b3-ba42-c39c-551814caf335@gmail.com>

On Mon, Mar 26, 2018 at 2:08 PM, Derrick Stolee <stolee@gmail.com> wrote:

> Since most heavily-used tools that didn't spawn Git processes use
> LibGit2 to interact with Git repos, I added Ed Thomson to CC to see
> if libgit2 could ever write these bad header comments.

We added the `sorted` capability to our `packed-refs` header relatively recently (approximately two months ago, v0.27.0 will be the first release to include it as of today). So, at the moment, libgit2 writes:

  "# pack-refs with: peeled fully-peeled sorted "

Prior to this change, libgit2's header was stable for the last five years as:

  "# pack-refs with: peeled fully-peeled "

And prior to that, we advertised only `peeled`:

  "# pack-refs with: peeled "

Thanks for thinking of us!

-ed