epriestley 06edcf2709 Fix an issue where ancestors of permanent refs might not be published during import or if a branch is later made permanent ... Summary: Fixes T13284. See that task for substantial discussion. There are currently two cases where we'll skip over commits which we should publish: - if a branch is not permanent, then later made permanent; or - in some cases, the first time we examine branches in a repository. In both cases, this error is one-shot and things work correctly going forward. The root cause is conflation between the states "this ref currently permanent" and "this ref was permanent the last time we updated refs". Separate these pieces of state and cover all these cases. Also introduce a "--rebuild" flag to fix the state of bad commits. Test Plan: See T13284 for the three major cases: - initial import; - push changes to a nonpermanent branch, update, then make it permanent; - push chanegs to a nonpermanent branch, update, push more changes, then make it permanent. Subscribers: PHID-OPKG-gm6ozazyms6q6i22gyam Maniphest Tasks: T13284 Differential Revision: https://secure.phabricator.com/D20829		2019-09-25 08:54:50 -07:00
..
autopatches	Fix an issue where ancestors of permanent refs might not be published during import or if a branch is later made permanent	2019-09-25 08:54:50 -07:00
patches	Make two ancient migrations fatal if they affect data	2019-02-06 17:08:34 -08:00
quickstart.sql	Update Quickstart SQL	2019-04-30 08:19:39 -07:00
stopwords.txt	Provide a setup warning about using the default MySQL stopword file	2014-08-13 15:34:09 -07:00
stopwords_myisam.txt	Show users how fulltext search queries are parsed and executed; don't query stopwords or short tokens	2017-04-12 19:07:54 -07:00