You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@maven.apache.org by el...@apache.org on 2023/02/19 14:43:56 UTC

[maven-doxia] 01/01: Clarify that it's OK to use spaces for things other than indentation

This is an automated email from the ASF dual-hosted git repository.

elharo pushed a commit to branch elharo-patch-1
in repository https://gitbox.apache.org/repos/asf/maven-doxia.git

commit 7ef80748884a2d2d29a669fe8b0905ec872f0c16
Author: Elliotte Rusty Harold <el...@users.noreply.github.com>
AuthorDate: Sun Feb 19 14:43:49 2023 +0000

    Clarify that it's OK to use spaces for things other than indentation
    
    Indeed, it's necessary,
---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 24a536b0..04a1ba79 100644
--- a/README.md
+++ b/README.md
@@ -56,7 +56,7 @@ There are some guidelines which will make applying PRs easier for us:
 + Make commits of logical units.
 + Respect the original code style: by using the same [codestyle][code-style],
   patches should only highlight the actual difference, not being disturbed by any formatting issues:
-  + Only use spaces for indentation.
+  + Use spaces for indentation, not tabs.
   + Create minimal diffs - disable on save actions like reformat source code or organize imports. 
     If you feel the source code should be reformatted, create a separate PR for this change.
   + Check for unnecessary whitespace with `git diff --check` before committing.