[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn commit: r14860 - branches/1.2.x

From: Daniel L. Rall <dlr_at_finemaltcoding.com>
Date: 2005-06-02 07:21:38 CEST

On Tue, 2005-05-31 at 10:00 -0500, Brian W. Fitzpatrick wrote:
> On Fri, 2005-05-27 at 17:22 -0700, Daniel L. Rall wrote:
> > On Fri, 2005-05-27 at 18:43 -0500, Brian W. Fitzpatrick wrote:
> > > On May 27, 2005, at 5:44 PM, Daniel L. Rall wrote:
> > >
> > > > Is there any interaction with this and the symlink permission issue
> > > > just posted about?
> > >
> > > I don't know... I haven't tested it any further, but seeing as we're
> > > still attempting to change the permissions on a link to a file that
> > > hasn't shown up yet, I'm pretty sure it's still broked (that is, that
> > > there's still a race).
> >
> > Is there any way we could wait to change permission on the file until it
> > shows up, and it it doesn't show up (e.g. wasn't checked out), perhaps
> > avoid trying to make the change or queue it up for later in some WC
> > admin file?
>
> I suppose we *could*, but I'd much rather not. I don't think that
> svn:needs-lock on a symlink should flip the write bit on its destination
> file--if you want this behavior on the destination, set the svn:needs-
> lock prop on the destination.

Thanks for explaining, sounds good.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jun 2 07:22:16 2005

This is an archived mail posted to the Subversion Dev mailing list.