This is an automated email from the git hooks/post-receive script.
unknown user pushed a change to branch akhuettel/tests-libgcc-3 in repository glibc.
discards ca72e6df89 elf: Remove now pointless empty ld.so.conf files in single tests discards ef4970a024 support: Always run ldconfig in containered tests discards 8c1d9194fb Makefile: Add ld.so.conf with libgcc dir to testroot.pristine discards bbb7025c76 Makeconfig: Add libgcc directory to rtld-prefix search path new 09791e4c29 Makeconfig: Add libgcc directory to rtld-prefix search path new 9ddebdcf8f Makefile: Add ld.so.conf with libgcc dir to testroot.pristine new f11fd2895a support: Always run ldconfig in containered tests new 190c947a35 elf: Remove now pointless empty ld.so.conf files in single tests
This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this:
* -- * -- B -- O -- O -- O (ca72e6df89) \ N -- N -- N refs/heads/akhuettel/tests-libgcc-3 (190c947a35)
You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B.
Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever.
The 4 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference.
Summary of changes: Makeconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)