> I think we should use "native" for eol style - this usually does not create > problems with different environments (I think this is already predefined for > most file types for our svn anyway). > For the code formatting, I prefer spaces as well... +1
On 10/11/07, Carsten Ziegeler (JIRA) <[EMAIL PROTECTED]> wrote: > > [ > https://issues.apache.org/jira/browse/SANSELAN-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534042 > ] > > Carsten Ziegeler commented on SANSELAN-1: > ----------------------------------------- > > I think we should use "native" for eol style - this usually does not create > problems with different environments (I think this is already predefined for > most file types for our svn anyway). > For the code formatting, I prefer spaces as well, but I think this is > something we can change after the first code drop. > > So, is anything preventing us from committing this stuff? > > > Initial code drop > > ----------------- > > > > Key: SANSELAN-1 > > URL: https://issues.apache.org/jira/browse/SANSELAN-1 > > Project: Sanselan > > Issue Type: New Feature > > Reporter: Craig Russell > > Assignee: Carsten Ziegeler > > Attachments: patch_init.zip > > > > > > This issue is to discuss the initial code drop into the project. > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online. > >
