On Thu, Apr 21, 2011 at 4:25 PM, Julian Foad wrote:
> Hyrum K Wright wrote:
>> On Thu, Apr 21, 2011 at 1:33 PM, Hyrum K Wright
>> wrote:
>> > On Thu, Apr 21, 2011 at 10:00 AM, Julian Foad
>> > wrote:
>> >> This is a post-1.7 RFC.
>> >>
>> >> Most libsvn_client APIs allow the caller to throw ei
Hyrum K Wright wrote:
> On Thu, Apr 21, 2011 at 1:33 PM, Hyrum K Wright wrote:
> > On Thu, Apr 21, 2011 at 10:00 AM, Julian Foad
> > wrote:
> >> This is a post-1.7 RFC.
> >>
> >> Most libsvn_client APIs allow the caller to throw either URLs or working
> >> copy paths at the API and then it just
On Thu, Apr 21, 2011 at 1:33 PM, Hyrum K Wright wrote:
> On Thu, Apr 21, 2011 at 10:00 AM, Julian Foad
> wrote:
>> This is a post-1.7 RFC.
>>
>> Most libsvn_client APIs allow the caller to throw either URLs or working
>> copy paths at the API and then it just does the right thing. But does
>> t
On Thu, Apr 21, 2011 at 20:33, Hyrum K Wright wrote:
> On Thu, Apr 21, 2011 at 10:00 AM, Julian Foad
> wrote:
>> This is a post-1.7 RFC.
>>
>> Most libsvn_client APIs allow the caller to throw either URLs or working
>> copy paths at the API and then it just does the right thing. But does
>> thi
On Thu, Apr 21, 2011 at 10:00 AM, Julian Foad wrote:
> This is a post-1.7 RFC.
>
> Most libsvn_client APIs allow the caller to throw either URLs or working
> copy paths at the API and then it just does the right thing. But does
> this paradigm make sense for APIs such as this one?
Julian,
Does t
On Thu, Apr 21, 2011 at 10:00 AM, Julian Foad wrote:
> This is a post-1.7 RFC.
I'm happy to make this a 1.7 RFC, since we're already rev'd the client
API, and the question is coming up now. The effort shouldn't be that
involved.[1]
-Hyrum
[1] Yes, I'm volunteering, and yes those are famous las
On Thu, Apr 21, 2011 at 11:00, Julian Foad wrote:
> This is a post-1.7 RFC.
If you have time and can do it for 1.7, then I don't think we can stop you :-P
>...
> Thoughts?
Yeah. Split them!
Cheers,
-g
On 21.04.2011 17:00, Julian Foad wrote:
This is a post-1.7 RFC.
Most libsvn_client APIs allow the caller to throw either URLs or working
copy paths at the API and then it just does the right thing. But does
this paradigm make sense for APIs such as this one?
svn_client_propset4() operates on e
This is a post-1.7 RFC.
Most libsvn_client APIs allow the caller to throw either URLs or working
copy paths at the API and then it just does the right thing. But does
this paradigm make sense for APIs such as this one?
svn_client_propset4() operates on either WC paths or URLs. Although its
purp
9 matches
Mail list logo