On Thu, Feb 21, 2008 at 2:50 PM, S M <smpub2000_at_yahoo.com> wrote:
>
>
> I want to checkin code, using TSVN on windows xp, for an existing cvs
> project to Subversion server installed on Solaris.
> I have the following questions:
> 1. The svnbook states that for file portability, the property
> "svn:eol-style" should be set to native. Can you specify how this is done
> using TSVN. I believe this would need to be set for all files in the
> project.
Right-click a file (or group of files), select TSVN ->Properties. You
can apply them on all new files added/imported via the auto-props
section of your Subversion client config.
Should it be done for all files? No, only plain-text, and only those
which will not be corrupted or otherwise changed in a material way by
changing EOL style. This setting doesn't guarantee portability, it
really just makes it easier to work on various client OSes with text
editors which may not understand EOL markers used by other OSes (e.g.,
Notepad doesn't understand UNIX EOLs).
> 2. IS svn:eol-style the only property that needs to be set in this case.
Depends upon your requirements.
> 3. Are there any tools to generate, or existing templates, for svnignore
> settings (by using .svnignore files?) for typical
> patterns (obj,.out, .class, war, jar, solaris packaging files etc) needed
> before importing a project into svn for the first time.
SVN uses the property svn:ignore to ignore files in directories, in
addition to the global-ignores section of your Subversion config file.
What items you decide to ignore really are up to you - my settings
won't map to your workspace.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-02-21 21:11:29 CET