Hi Martin, It seems it's in the `master` branch: https://github.com/llvm/llvm-project/commit/78a57069b53a08d5aef98a8472fcfa73dbbc8771
So, is the problem resolved? On Mon, Dec 7, 2020 at 11:12 AM Martin Storsjö via cfe-dev <cfe-...@lists.llvm.org> wrote: > > Hi, > > On Sun, 6 Dec 2020, Mike Edwards via llvm-dev wrote: > > > The change to the default branch setting has been completed. The new > > default branch for the llvm-project is now 'main'. Pushes to the 'master' > > branch will no longer be accepted. Please update your workflow to use the > > new 'main' branch. Thank you for your patience and cooperation during this > > process. I hope everyone has a nice, productive day. > > I just pushed a patch to the new main branch, and I've noticed these > issues: > > - The master branch isn't updated to reflect this. Afaik it was supposed > that the master branch, while read only, would still receive updates until > it's being discontinued - or did I misunderstand that bit? > > - Phabricator doesn't seem to pick up on commits to master, and doesn't > autoclose reviews based on pushed patches. I guess this would be fixed by > either making it track the main branch, or if new commits are mirrored > into the previous branch until Phabricator is switched? > > // Martin > _______________________________________________ > cfe-dev mailing list > cfe-...@lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev -- With best regards, Anton Korobeynikov Department of Statistical Modelling, Saint Petersburg State University _______________________________________________ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
