Update master to latest libgit2 and build statically #362

2017-01-20T07:55:05-06:00

carlosmn commented

2017-01-20 07:55:05 -06:00

(Migrated from github.com)

We have the versioned branches in order to match a libgit2 version, and next to follow the tip of libgit2. master used to follow whatever the latest versioned branch was, but that meant having to update two branches to be the same, which means extra things to remember when trying to update.

This also means that following master is essentially impossible to do reliably, since it would change the expected version of libgit2 from under you, or your package manager would.

This updates master to take on the role that next used to have and does away with a stable-but-not-really branch. The versioned branches stay.

We have the versioned branches in order to match a libgit2 version, and `next` to follow the tip of libgit2. `master` used to follow whatever the latest versioned branch was, but that meant having to update two branches to be the same, which means extra things to remember when trying to update. This also means that following `master` is essentially impossible to do reliably, since it would change the expected version of libgit2 from under you, or your package manager would. This updates `master` to take on the role that `next` used to have and does away with a stable-but-not-really branch. The versioned branches stay.

Sign in to join this conversation.

No reviewers