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

Re: "not under version control" error - continued

From: Philip Martin <philip_at_codematters.co.uk>
Date: 2004-02-11 21:42:05 CET

Ben Collins-Sussman <sussman@collab.net> writes:

> /* Don't do the props_changed stuff if this is a dry_run and we don't
> have an access baton, since in that case the file will already have
> been recognised as added, in which case they cannot conflict. A

The problem case is "dry run and added", and in this case the
props_changed stuff should be avoided.

> similar argument applies to directories in close_directory. */
> if (b->propchanges->nelts > 0 && (! eb->dry_run || adm_access))
> {
> SVN_ERR (eb->diff_callbacks->props_changed
> (adm_access, &prop_state,
> b->wcpath,
> b->propchanges, b->pristine_props,
> b->edit_baton->diff_cmd_baton));
> }
>
> I made a tiny patch to this condition:
>
> - if (b->propchanges->nelts > 0 && (! eb->dry_run || adm_access))
> + if (b->propchanges->nelts > 0 && (! eb->dry_run) && adm_access)
>
> ...and it fixes the problem, but causes merge_test #4 to fail. What's
> the correct logic here? Philip? Anyone?

How about

  if (b->propchanges->nelts > 0 && (! (eb->dry_run && b->added)))

-- 
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Feb 11 21:42:57 2004

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.