Erik Huelsmann wrote:
> On 4/2/07, Peter Lundblad <plundblad@google.com> wrote:
>> dionisos@tigris.org writes:
>> > http://subversion.tigris.org/issues/show_bug.cgi?id=2474
>> >
>> >
>> >
>> > User dionisos changed the following:
>> >
>> > What |Old value |New value
>> >
>> ================================================================================
>>
>> > Target milestone|--- |2.0
>> >
>> --------------------------------------------------------------------------------
>>
>> >
>> >
>> >
>> >
>> > ------- Additional comments from dionisos@tigris.org Sun Apr 1
>> 12:52:40 -0700 2007 -------
>> > Move into 2.0, since this changes our API.
>> >
>>
>> Hi, Erik,
>>
>> In what way does this change our API?
>
> The output of the client has been declared a scripting API (long ago).
> Implementing this change would break that in the way that scripts and
> other programs using our client may depend on the current format of
> <filename>.rXXX.
I've always understood "the output of the client" to be limited mostly to
what gets printed to stdout as part of normal processing. The names of
conflicts files, therefore, are in my opinion, *not* part of the API.
Besides, we provide ways to programmatically ask what the conflict file
names are ('svn info' lists them, and the underlying APIs reveal them)
specifically *because* you can't know for sure what they will be called (due
to our use of svn_io_open_unique_file()).
--
C. Michael Pilato <cmpilato@collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
Received on Mon Apr 2 18:44:07 2007