On Mon, Mar 09, 2009 at 01:36:26AM -0400, Matt McCutchen wrote:
> From the code, it looks like comments (as lines beginning with '#' or
> ';') are supported but are buggy on remote runs (probably what you are
> seeing).
Yeah, the code is supposed to ignore comments unless the data is coming
in via
Felipe
On Tue, Mar 10, 2009 at 12:04 AM, Matt McCutchen wrote:
> On Mon, 2009-03-09 at 20:56 +1000, Felipe Alvarez wrote:
>> On Mon, Mar 9, 2009 at 3:36 PM, Matt McCutchen
>> wrote:
>> > Since a major purpose of --files-from is to specify arbitrary filenames
>> > safely, I think comments shou
On Mon, 2009-03-09 at 20:56 +1000, Felipe Alvarez wrote:
> On Mon, Mar 9, 2009 at 3:36 PM, Matt McCutchen wrote:
> > Since a major purpose of --files-from is to specify arbitrary filenames
> > safely, I think comments should not be supported, at least not when
> > --from0 is specified. Wayne? On
On Mon, Mar 9, 2009 at 3:36 PM, Matt McCutchen wrote:
> On Sun, 2009-03-08 at 11:14 +1000, Felipe Alvarez wrote:
>> I'm using --files-from=FILE. 'FILE' contains some lines beginning with
>> '#' for comments, but rsync thinks they are files. Are comments
>> supported in --files-from=FILE?
>
> The d
On Sun, 2009-03-08 at 11:14 +1000, Felipe Alvarez wrote:
> I'm using --files-from=FILE. 'FILE' contains some lines beginning with
> '#' for comments, but rsync thinks they are files. Are comments
> supported in --files-from=FILE?
The documentation doesn't say. From the code, it looks like comment
I'm using --files-from=FILE. 'FILE' contains some lines beginning with
'#' for comments, but rsync thinks they are files. Are comments
supported in --files-from=FILE?
Felipe
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lis
