Re: Change in reporting for --dry-run in 2.6.x

2004-01-28 Thread Phil Howard
On Wed, Jan 28, 2004 at 12:38:11PM -0500, Alberto Accomazzi wrote: | I just noticed that there is an extra blank line in the output generated | by rsync when the --dry-run (-n) flag is used. This seems to have | started with 2.6.0. Is this desired? The reason why I'm asking is | because I us

Re: Change in reporting for --dry-run in 2.6.x

2004-01-28 Thread Wayne Davison
On Wed, Jan 28, 2004 at 12:38:11PM -0500, Alberto Accomazzi wrote: > I just noticed that there is an extra blank line in the output generated > by rsync when the --dry-run (-n) flag is used. This seems to have > started with 2.6.0. Is this desired? The NEWS file has this (understated statement

Re: Change in reporting for --dry-run in 2.6.x

2004-01-28 Thread jw schultz
On Wed, Jan 28, 2004 at 12:38:11PM -0500, Alberto Accomazzi wrote: > I just noticed that there is an extra blank line in the output generated > by rsync when the --dry-run (-n) flag is used. This seems to have > started with 2.6.0. Is this desired? The reason why I'm asking is > because I use

Change in reporting for --dry-run in 2.6.x

2004-01-28 Thread Alberto Accomazzi
I just noticed that there is an extra blank line in the output generated by rsync when the --dry-run (-n) flag is used. This seems to have started with 2.6.0. Is this desired? The reason why I'm asking is because I use scripts that parse the output from rsync and little modifications in verb