Xavier Morel 0f4c22490c [IMP] forwardport: refs ... There's an issue of too many commits being selected for cherry-picking. It still isn't quite clear, but the forward ports to 11.0 systematically seem to get everything from 5045b5f4c346e60c9b127403ef1fde453d49396a to the PR head, and that commit was one of the first to land after the last merge-based forward port. So the commits selection seems to behave as if the commits range was `..origin/pull/36692` rather than the `origin/10.0..origin/pull/36692` which is passed to rev-list. This might be an issue of concurrent access / update of the refs (though I can't reproduce it locally, missing refs generate an error). This change attempts to "pin" the local branch in the working copy rather than go and get it from the repo. It's unclear that this will change / fix anything, but it might just work. Also stop creating shared clones, that seems like an unnecessary risk (and might be the actual source of the issue).		2019-09-12 09:05:49 +02:00
..
__init__.py	[ADD] forwardbot	2019-09-05 10:00:07 +02:00
forwardport.py	[ADD] forwardbot	2019-09-05 10:00:07 +02:00
project.py	[IMP] forwardport: refs	2019-09-12 09:05:49 +02:00