You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@arrow.apache.org by do...@apache.org on 2023/04/23 12:21:32 UTC

[arrow] branch dom/minor created (now 6a2978505b)

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

domoritz pushed a change to branch dom/minor
in repository https://gitbox.apache.org/repos/asf/arrow.git


      at 6a2978505b MINOR: clarify when to use minor

This branch includes the following new commits:

     new 6a2978505b MINOR: clarify when to use minor

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.



[arrow] 01/01: MINOR: clarify when to use minor

Posted by do...@apache.org.
This is an automated email from the ASF dual-hosted git repository.

domoritz pushed a commit to branch dom/minor
in repository https://gitbox.apache.org/repos/asf/arrow.git

commit 6a2978505be42140b923e83c46553d7d35716659
Author: Dominik Moritz <do...@gmail.com>
AuthorDate: Sun Apr 23 14:21:24 2023 +0200

    MINOR: clarify when to use minor
---
 CONTRIBUTING.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index a1c473a24b..5ad7ca2486 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -50,7 +50,7 @@ makes it easier for us to process the backlog of submitted Pull Requests.
 
 Any functionality change should have a GitHub issue opened. For minor changes that
 affect documentation, you do not need to open up a GitHub issue. Instead you can
-prefix the title of your PR with "MINOR: " if meets the following guidelines:
+prefix the title of your PR with "MINOR: " if meets one of the following:
 
 *  Grammar, usage and spelling fixes that affect no more than 2 files
 *  Documentation updates affecting no more than 2 files and not more