On 17. 6. 25 09:45, Daniel Sahlberg wrote:
I personally think it should be possible to specify any legal
filenames in the --targets file. Files with preceding or trailing
whitespace is possible under Linux. It seems NTFS also allow this but
the Windows shell trim both ends, cmd.exe allow creati
IMO it's necessary to distinguish server errors:
- "data errors" like files have been deleted. Then issue a warning and
continue processing.
- and other errors (e.g. internal server error etc.) where processing may stop.
Andy
On Tue, 17 Jun 2025 at 13:34, Lorenz via users
wrote:
>
> Hi,
>
> th
On 17. 6. 25 09:45, Daniel Sahlberg wrote:
Den tis 17 juni 2025 kl 06:24 skrev Yasuhito FUTATSUKI
:
Hello,
On 2025/06/16 18:06, 管理员 wrote:
> If the file name ends with a space, it cannot be save to a file
then use the --targets options:
>
> For example:
>
> File
Hi,
the non-exiting file case is handled by the client.
It generates a warning that the file does not exist in the local
database and/or in the file system.
I would assume there are different messages for the two cases.
in the deleted file case the wrror is generated by the server.
The files exis
On Jun 17, 2025, at 02:45, Daniel Sahlberg wrote:
> Files with preceding or trailing whitespace is possible under Linux. It seems
> NTFS also allow this but the Windows shell trim both ends, cmd.exe allow
> creating files with preceding whitespace. I haven't checked macOS.
macOS, being a POSIX-
Den tis 17 juni 2025 kl 06:24 skrev Yasuhito FUTATSUKI <
futat...@yf.bsdclub.org>:
> Hello,
>
> On 2025/06/16 18:06, 管理员 wrote:
> > If the file name ends with a space, it cannot be save to a file then use
> the --targets options:
> >
> > For example:
> >
> > Files:
> >
> > /Users/abc/trunk/aaa
> >
