On Sep 22, 2012, at 13:26, Alexei Baranov wrote:
> I suppose SVN library for Windows has a bug. I've created file named
> PRN.RPGLE in working copy on my IBM i system. This file was successfully
> committed to SVN server. Next, I've tried to check it out to working copy on
> my Windows PC. Che
[snip]
> It's not a bug in Subversion; it's a "feature" (or at least a
> reality that's unlikely to change) of the Windows operating
> system. On Windows, you may not create a file whose name is
> "PRN", with any extension.
It would be a great benefit for the user if SVN warns about that fact
On Sep 24, 2012, at 03:17, Andreas Tscharner wrote:
>
>> It's not a bug in Subversion; it's a "feature" (or at least a
>> reality that's unlikely to change) of the Windows operating
>> system. On Windows, you may not create a file whose name is
>> "PRN", with any extension.
>
> It would be a
On Mon, Sep 24, 2012 at 12:57:38AM -0500, Ryan Schmidt wrote:
> It's not a bug in Subversion; it's a "feature" (or at least a
> reality that's unlikely to change) of the Windows operating system.
> On Windows, you may not create a file whose name is "PRN", with any
> extension.
Actually, it *is*
> -Original Message-
> From: Ryan Schmidt [mailto:subversion-20...@ryandesign.com]
> Sent: 24 September 2012 09:22
> To: Andreas Tscharner
> Cc: Alexei Baranov; users@subversion.apache.org
> Subject: Re: SVN and PRN and CON files on Windows platform
>
>
>
Am 24.09.2012 10:52, schrieb Cooke, Mark:
-Original Message- From: Ryan Schmidt
Subversion can't really know if you care about Windows
compatibility. Many people don't.
What you can do though, if you care about Windows compatibility, is
to write a pre-commit hook script that prevents the
On Mon, Sep 24, 2012 at 4:21 AM, Ryan Schmidt
wrote:
>
> On Sep 24, 2012, at 03:17, Andreas Tscharner wrote:
>>
>>> It's not a bug in Subversion; it's a "feature" (or at least a
>>> reality that's unlikely to change) of the Windows operating
>>> system. On Windows, you may not create a file whose
