> Date: Fri, 26 May 2017 09:30:53 -0700 > From: Joel Brobecker <brobec...@adacore.com> > Cc: DJ Delorie <d...@redhat.com>, gcc-patches@gcc.gnu.org, > gdb-patc...@sourceware.org > > Normally, I'd expect someone pushing to GCC's libibert to also > update our repo accordingly. However, it's easy to forget so, > if you notice a change that was not propagated to us, we just > cherry-pick those changes so as to make sure our copy is up > to date with GCC's. We also see the occasional "resync libiberty" > commits which act as a failsafe, but I don't think we should wait > for one of those.
What can I do to expedite the process? This currently holds the 8.0 release, and I'm uneasy to be the culprit. > Should those ones be pushed to the gdb-8.0-branch as well? Yes.
