Google Git
Sign in
chromium / chromiumos / platform / redaction_tool / refs/heads/firmware-ec-R137-16267.2.B
commit549cb26169ad4f6e8bc9dfcbd9687cd7445dfc50[log] [tgz]
authorNathan Muggli <[email protected]>Thu Jan 30 18:31:13 2025
committerChromeos LUCI <[email protected]>Wed Feb 05 23:04:06 2025
tree72ed2ae113d4a4cc18025fbb513f24c488118f56
parent2543a686a5805d8d2e25a4e4f107c778519f4632 [diff]
redaction_tool: Switch from base::ranges to std::ranges

CL:6215440 removes base::ranges.  Switch to std::ranges so a
compatibility patch in libchrome can be removed.

BUG=b:393368038
TEST=CQ

Change-Id: I2f920a51ecf3763cea9e4f3f20b7e7a19ef32ede
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/redaction_tool/+/6219452
Reviewed-by: Ahmed Fakhry <[email protected]>
Tested-by: Kevin Lin <[email protected]>
Commit-Queue: Nathan Muggli <[email protected]>
3 files changed
tree: 72ed2ae113d4a4cc18025fbb513f24c488118f56
  1. BUILD.gn
  2. DIR_METADATA
  3. ip_address.cc
  4. ip_address.h
  5. libmetrics_metrics_recorder.cc
  6. libmetrics_metrics_recorder.h
  7. libmetrics_metrics_tester.cc
  8. libmetrics_metrics_tester.h
  9. metrics_tester.h
  10. OWNERS
  11. pii_types.h
  12. PRESUBMIT.cfg
  13. README.md
  14. redaction_tool.cc
  15. redaction_tool.h
  16. redaction_tool_metrics_recorder.h
  17. redaction_tool_unittest.cc
  18. url_canon.h
  19. url_canon_internal.cc
  20. url_canon_internal.h
  21. url_canon_ip.cc
  22. url_canon_ip.h
  23. url_canon_stdstring.cc
  24. url_canon_stdstring.h
  25. url_parse.h
  26. validation.cc
  27. validation.h
README.md

redaction_tool: PII Redaction Tool

A redaction_tool redacts PII using a wide set of RegEx expressions.

This code is a mirror of https://source.chromium.org/chromium/chromium/src/+/main:components/feedback/redaction_tool/

Changes should be made in chromium code base only and then be upreved here.

How to update the source

To pull in updates from chromium/src, do the following:

  • git remote update
  • git checkout -b main cros/main
  • git merge cros/upstream/main
    • BUILD.gn should mostly use the version from main, unless the upstream changes the files to be built.
    • The #include paths should use the version from main (without “components/feedback”). This should be the majority of the merge conflicts.
    • In the commit message of the merge, list the commits from upstream that are merged.
    • If you need to make changes to the merged commits (outside of conflicts), do that work in separate commits. For example, if you need to revert commits, use git revert after committing the merge commit. This preserves the history and makes it clear why a change is being reverted rather than quietly changing it in the merge commit.
    • Check the changes introduced by your merge by doing a diff against the commit before the merge. The difference should be the same as the changes in the upstream.
  • Push the resulting merge commit for review with:
    • git push HEAD:refs/for/main