jerry gay wrote:
On 2/11/07, via RT Paul Cochrane <[EMAIL PROTECTED]> wrote:
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #41485]
# in the subject line of all future correspondence about this issue.
# <URL: http://rt.perl.org/rt3/Ticket/Display.html?id=41485 >
svn:eol-style should be set to 'native', so it'll save files with the
line ending the platform expects. the only exceptions i'm aware of are
examples using file io. as the tests are currently designed, these
require svn:eol-style=LF (see t/examples/streams.t for more.)
Apropos the discussion in this thread, should any svn properties be set
on files submitted as patches or new files?
Or is this not relevant, as such files cannot yet have svn properties?
But perhaps more to the point: Suppose that I am committing new files
to a *branch* (e.g., the buildtools branch) -- files that ultimately
will be submitted to the project as patches/new files to *trunk*. What
svn properties should I set on files I'm committing to my branch?
(So far, I'm just adding 'svn:keywords "Id"', because otherwise I don't
get proper updates in my svn Id tags.)
kid51
