release date for rsync 2.5.7?

[jw schultz]

On Thu, May 01, 2003 at 05:36:57PM -0700, Manish Dubey wrote:
> --- jw schultz <jw at pegasys.ws> wrote:
> > On Thu, May 01, 2003 at 11:53:35AM -0700, Manish
> > Dubey wrote:
> > > I am looking to upgrade to latest version of
> > rsync.
> > > However there are some critical bug fixes (for my
> > > needs) that have been commited to CVS post 2.5.6
> > > release.
> > > 
> > > Can anyone tell me how i can find out the release
> > > schedule for 2.5.7? I looked around at rsync home
> > page

Bad line wrapping.  A mailer should not change wrapping on
quoted text.  If wrapping must be changed it should be done
in a way that doesn't break the quoting.

> > > and did not see how i can access schedule/timeline
> > for
> > > official releases.
> > > 
> > > I can work with latest in CVS if the release date
> > is
> > > too far out, else i would like to use offical
> > release.
> > 
> > There is no release schedule.  Releases are made
> > when the
> > rsync team feels the code is stable, has enough
> > changes to
> > merit a release or enough bugfixes to make current
> > obsolete,
> > and an rsync developer willing to spend the time
> > doing a
> > release.
> > 
> > Which bugfix is your motivation?  We'll consider
> > your imput
> > as a vote for a release.
> 
> 
> I am specifically interested in the bug fix for
> --link-dest when rsync is invoked without the flags
> preserve permissions/ownership.
> 
> Also, since you are accepting my input. I would also
> like to request a minor feature :-). What will it take
> to have rsync create remote subdirectory tree
> recursively?
> 
> something like:
> 
> rsync some/local/files/*
> remote:/some/non/exist/dir/path/
> 
> Looks like someone asked for this in FAQ-o-matic too.
> 
> http://rsync.samba.org/fom-serve/cache/213.html

What it will take is someone actually coding it and the
assent of the developers.

I'm inclined to discourage such a change.  rsync is modeled
on cp and cp would fail if the destination directory is
missing.  Furthermore, failing on missing directory is a
valuable safety-net.  The majority of the time the
destination directory doesn't exist it is because of an
error.  Far better to have rsync to report "rsync: mkdir
/hoem/henry/Mail: No such file or directory" than to have
root or another wrong filesystem fill up on either system.

It is very easy to force the directory to exist.  Just
preceede rsync with "mkdir -p" if you know beyond doubt that
the directory, as specified, needs to be created.

-- 
________________________________________________________________
	J.W. Schultz            Pegasystems Technologies
	email address:		jw at pegasys.ws

		Remember Cernan and Schmitt