[libcxx-commits] [libcxx] [libc++] use copy_file_range for fs::copy (PR #109211)

[via libcxx-commits]

Jannik =?utf-8?q?Glückert?= <jannik.glueckert at gmail.com>,Louis Dionne
 <ldionne.2 at gmail.com>,Louis Dionne <ldionne.2 at gmail.com>,Louis Dionne
 <ldionne.2 at gmail.com>,
Jannik =?utf-8?q?Glückert?= <jannik.glueckert at gmail.com>,
Jannik =?utf-8?q?Glückert?= <jannik.glueckert at gmail.com>,
Jannik =?utf-8?q?Glückert?= <jannik.glueckert at gmail.com>
Message-ID:
In-Reply-To: <llvm.org/llvm/llvm-project/pull/109211 at github.com>


github-actions[bot] wrote:

<!--LLVM BUILDBOT INFORMATION COMMENT-->

@Jannik2099 Congratulations on having your first Pull Request (PR) merged into the LLVM Project!

Your changes will be combined with recent changes from other authors, then tested by our [build bots](https://lab.llvm.org/buildbot/). If there is a problem with a build, you may receive a report in an email or a comment on this PR.

Please check whether problems have been caused by your change specifically, as the builds can include changes from many authors. It is not uncommon for your change to be included in a build that fails due to someone else's changes, or infrastructure issues.

How to do this, and the rest of the post-merge process, is covered in detail [here](https://llvm.org/docs/MyFirstTypoFix.html#myfirsttypofix-issues-after-landing-your-pr).

If your change does cause a problem, it may be reverted, or you can revert it yourself. This is a normal part of [LLVM development](https://llvm.org/docs/DeveloperPolicy.html#patch-reversion-policy). You can fix your changes and open a new PR to merge them again.

If you don't get any reports, no action is required from you. Your changes are working as expected, well done!


https://github.com/llvm/llvm-project/pull/109211