Add note on using git-clang-format and clang-format-diff.py.
Remove the `clang-format` from the required items of PR as it's not enforced
anymore. It's now handled by regular code review.
Refs #242
Signed-off-by: Marc Poulhiès <dkm@kataplop.net>
This updates the contributor guide to let people know the update applys to
gccrs.
Co-authored-by: CohenArthur <arthur.cohen@epita.fr>
Co-authored-by: Marc Poulhiès <dkm@kataplop.net>
We have been accepting patches via mail from developers following the normal GCC processes. Let's update our guidelines to reflect this.
Co-authored-by: CohenArthur <arthur.cohen@epita.fr>
Co-authored-by: Thomas Schwinge <thomas@codesourcery.com>
Co-authored-by: Miguel Ojeda <ojeda@users.noreply.github.com>
... as discussed in
<https://gcc-rust.zulipchat.com/#narrow/stream/266897-general/topic/Testsuite.20results>:
> [...] best practice from what other GCC testsuites are doing), which I hope
> makes clearer the difference between the individual GCC/Rust testsuites:
> 'rust.test/compile' -> 'rust/compile/torture'
> 'rust.test/execute' -> 'rust/execute/torture'
> 'rust.test/unsupported' -> 'rust/compile/xfail'
> 'rust.test/xfail_compile' -> 'rust/compile'
... plus corresponding documentation updates in the '*.exp' files and
elsewhere.
This provides context for people learning to submit code or issues back to
the project. It will help answer frequently asked questions and a set of
rules for all of us to follow.
This is something that should evolve over time.
@mvvsmk
Marc Poulhiès
Thomas Schwinge
Thomas Schwinge
Philip Herron