Yuri Schimke <******@****.***> 1735306796 +0200

Yuri Schimke <******@****.***> 1758435742 +0100

Yuri Schimke <******@****.***> 1644968312 +0000

      ImmutableList.Builder<String> builder = ImmutableList.builder();
      assertThrows(NullPointerException.class, () -> builder.addAll((Iterable<String>) null));
    }

    {
      ImmutableList.Builder<String> builder = ImmutableList.builder();
      assertThrows(NullPointerException.class, () -> builder.addAll((Iterator<String>) null));
    }

    {
      ImmutableList.Builder<String> builder = ImmutableList.builder();

Yuri Schimke <******@****.***> 1710686794 +0000

Yuri Schimke <******@****.***> 1758435742 +0100

Yuri Schimke <******@****.***> 1758435742 +0100

Yuri Schimke <******@****.***> 1758435742 +0100

unnecessary redirection from ci/latest.txt to ci-cross/latest.txt. Users should know exactly where the builds are stored on Google Cloud storage buckets from now on. For example for 1.9 and 1.10, users can specify ci/latest-1.9 and ci/latest-1.10 as the CI build jobs what build images correctly updates those. The CI jobs for master update the ci-cross/latest location, so if you are looking for latest master builds, then the correct parameter to use would be ci-cross/latest. ([#63504](https://github.com/ku...

    ImmutableSetMultimap.Builder<String, Integer> builder = ImmutableSetMultimap.builder();
    builder.put("b", 3);
    builder.put("d", 2);
    builder.put("a", 5);
    builder.orderValuesBy(Collections.reverseOrder());
    builder.put("c", 4);
    builder.put("a", 2);
    builder.put("b", 6);
    ImmutableSetMultimap<String, Integer> multimap = builder.build();