On Jan 12, 2005, at 3:23 PM, dev wrote:
> Ben Collins-Sussman wrote:
>
>>
>>> Doesn't that seem to not fit with the subversion philosophy of
>>> making commands work consistently (if not always what one might have
>>> assumed)?
>>> Update and Commit normally work recursively in a WC. It seems to me
>>> that the right thing to do in this case is to apply both the update
>>> and the commit in the same way with regard to svn:externals.
>>>
>>
>> Yes, it's a known bug (or rather, incomplete feature).
>
>
> When will this feature be implemented completely?
>
> I miss this feature from cvs in bigger projects.
>
Hmm, it's issue 1167:
http://subversion.tigris.org/issues/show_bug.cgi?id=1167
Apparently it's been floating out in "unscheduled" space forever.
I originally thought someone had tried and failed to do it, discovering
it was very hard. But talking to my officemates, that seems not to be
the case. I think it's just that nobody's gotten around to it. kfogel
says that some developers feel that the issue should probably be part
of a "larger rewrite" of the svn:externals feature, so maybe that's why
it's not had much inertia.
In any case, cmpilato thinks it would be pretty easy for someone to
implement. It's just a matter of teaching svn_client_commit() to loop
over the list of externals and make more commits. (Since the externals
are often from different repositories, we couldn't possibly make one
giant atomic commit.)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jan 12 22:47:54 2005