[all-commits] [llvm/llvm-project] 0e1481: [libc][bazel] Define libc namespace in a separate ...

[Guillaume Chatelet via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 0e1481439f11c4b9d7a27ef7df7404c0990044b4
      https://github.com/llvm/llvm-project/commit/0e1481439f11c4b9d7a27ef7df7404c0990044b4
  Author: Guillaume Chatelet <gchatelet at google.com>
  Date:   2023-10-10 (Tue, 10 Oct 2023)

  Changed paths:
    M utils/bazel/llvm-project-overlay/libc/BUILD.bazel
    A utils/bazel/llvm-project-overlay/libc/libc_namespace.bzl

  Log Message:
  -----------
  [libc][bazel] Define libc namespace in a separate file and drop the `release` flag (#68563)

The `release` flag is misleading and its semantics are not well defined.
Originally this was meant to allow for different `LIBC_NAMESPACE`
depending on whether the code was considered stabled and released or
unstable. It appears that we may have a canary environment that is
neither released or dev. As a consequence we move the `LIBC_NAMESPACE`
definition to its own file and each environment can override this file
with whatever makes sense.