You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sandeep Tata (JIRA)" <ji...@apache.org> on 2009/03/30 20:47:50 UTC
[jira] Created: (CASSANDRA-23) Formatting guidelines
Formatting guidelines
---------------------
Key: CASSANDRA-23
URL: https://issues.apache.org/jira/browse/CASSANDRA-23
Project: Cassandra
Issue Type: Task
Environment: all
Reporter: Sandeep Tata
Priority: Minor
Attachments: formatting-conventions.xml
Include code formatting guidelines to help produce cleaner patches and avoid introducing unnecessary indentation/spacing issues.
The project site/wiki is probable the right place for this.
I'm attaching my (updated) ruleset that I use in Eclipse. I don't know if this complies 100% with the conventions used in Cassandra, but seems close enough.
If the other developers have similar rulesets for vim/emacs/other IDEs, that might help too.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CASSANDRA-23) Formatting guidelines
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12693877#action_12693877 ]
Jonathan Ellis commented on CASSANDRA-23:
-----------------------------------------
can you make a patch vs the one here, if necessary?
http://incubator.apache.org/cassandra/developers.html
> Formatting guidelines
> ---------------------
>
> Key: CASSANDRA-23
> URL: https://issues.apache.org/jira/browse/CASSANDRA-23
> Project: Cassandra
> Issue Type: Task
> Environment: all
> Reporter: Sandeep Tata
> Priority: Minor
> Attachments: formatting-conventions.xml
>
>
> Include code formatting guidelines to help produce cleaner patches and avoid introducing unnecessary indentation/spacing issues.
> The project site/wiki is probable the right place for this.
> I'm attaching my (updated) ruleset that I use in Eclipse. I don't know if this complies 100% with the conventions used in Cassandra, but seems close enough.
> If the other developers have similar rulesets for vim/emacs/other IDEs, that might help too.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (CASSANDRA-23) Formatting guidelines
Posted by "Sandeep Tata (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sandeep Tata closed CASSANDRA-23.
---------------------------------
Resolution: Fixed
Guidelines available at http://incubator.apache.org/cassandra/developers.html
> Formatting guidelines
> ---------------------
>
> Key: CASSANDRA-23
> URL: https://issues.apache.org/jira/browse/CASSANDRA-23
> Project: Cassandra
> Issue Type: Task
> Environment: all
> Reporter: Sandeep Tata
> Priority: Minor
> Attachments: formatting-conventions.xml
>
>
> Include code formatting guidelines to help produce cleaner patches and avoid introducing unnecessary indentation/spacing issues.
> The project site/wiki is probable the right place for this.
> I'm attaching my (updated) ruleset that I use in Eclipse. I don't know if this complies 100% with the conventions used in Cassandra, but seems close enough.
> If the other developers have similar rulesets for vim/emacs/other IDEs, that might help too.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CASSANDRA-23) Formatting guidelines
Posted by "Sandeep Tata (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12694889#action_12694889 ]
Sandeep Tata commented on CASSANDRA-23:
---------------------------------------
The format in http://incubator.apache.org/cassandra/developers.html seems close too. The only difference seems to be that the existing code probably uses a mix of tabs and spaces for indentation while the format posted on the website uses all spaces. I'm fine with switching over to that. I'm marking this issue resolved.
> Formatting guidelines
> ---------------------
>
> Key: CASSANDRA-23
> URL: https://issues.apache.org/jira/browse/CASSANDRA-23
> Project: Cassandra
> Issue Type: Task
> Environment: all
> Reporter: Sandeep Tata
> Priority: Minor
> Attachments: formatting-conventions.xml
>
>
> Include code formatting guidelines to help produce cleaner patches and avoid introducing unnecessary indentation/spacing issues.
> The project site/wiki is probable the right place for this.
> I'm attaching my (updated) ruleset that I use in Eclipse. I don't know if this complies 100% with the conventions used in Cassandra, but seems close enough.
> If the other developers have similar rulesets for vim/emacs/other IDEs, that might help too.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CASSANDRA-23) Formatting guidelines
Posted by "Sandeep Tata (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sandeep Tata updated CASSANDRA-23:
----------------------------------
Attachment: formatting-conventions.xml
> Formatting guidelines
> ---------------------
>
> Key: CASSANDRA-23
> URL: https://issues.apache.org/jira/browse/CASSANDRA-23
> Project: Cassandra
> Issue Type: Task
> Environment: all
> Reporter: Sandeep Tata
> Priority: Minor
> Attachments: formatting-conventions.xml
>
>
> Include code formatting guidelines to help produce cleaner patches and avoid introducing unnecessary indentation/spacing issues.
> The project site/wiki is probable the right place for this.
> I'm attaching my (updated) ruleset that I use in Eclipse. I don't know if this complies 100% with the conventions used in Cassandra, but seems close enough.
> If the other developers have similar rulesets for vim/emacs/other IDEs, that might help too.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.