[
https://issues.apache.org/jira/browse/PIG-3008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485787#comment-13485787
]
Cheolsoo Park commented on PIG-3008:
------------------------------------
I don't think that we should enforce a coding style, but we should definitely
enforce an indent style:
- No tabs.
- No trailing white spaces.
- 4 spaces to indent the code.
In addition to Jon's suggestion for fixing up old files, we should also allow
white space changes to a limited extend in any patch. For example, if I am
touching a method in a file, I should be able to fix white spaces in that area
of code that I'm touching regardless how long that file has not been modified.
Fixing an entire file could be disruptive, but fixing parts of a file should be
acceptable, no?
> Fix whitespace in Pig code
> --------------------------
>
> Key: PIG-3008
> URL: https://issues.apache.org/jira/browse/PIG-3008
> Project: Pig
> Issue Type: Improvement
> Reporter: Jonathan Coveney
> Fix For: 0.12
>
>
> This JIRA exists mainly to get a conversation started. We've talked about it
> before, and it's a tricky issue. That said, some of the Pig code is super,
> super gnarly. We need some sort of path that will let it eventually be
> fix-able.
> I posit: any file that hasn't been touched for over 6 months is eligible for
> a whitespace patch.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
