You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Alexander Haley <ah...@meditech.com> on 2013/08/07 17:38:20 UTC
Re: xml output changed - relative paths now appearing?
On Tue, Jul 16, 2013 at 6:26 AM, Bert Huijben <be...@qqmail.nl> wrote:
> > -----Original Message-----
> > With 1.7 I get
> >
> > <target
> > path="/home/pm/sw/subversion/obj/wc">
> > <entry
> > path="/home/pm/sw/subversion/obj/wc/foo">
> >
> > while with 1.8 I get
> >
> > <target
> > path="/home/pm/sw/subversion/obj/wc">
> > <entry
> > path=".">
>
> This appears wrong to me.
> svn status always gave the paths in the same form as how the user passed
> them, in both non-xml and xml form.
>
> I would guess that a lot of scripts break down if the paths don't match the
> form that they expected from all previous versions.
>
> I think we should revert to the old form, where the input path dictates the
> form in which we provide paths. Certainly for the --xml option, any other
> form will break scripts.
>
So - where does this stand - having an informal list agreement that this
is an issue - should I be submitting an issue formally- consider me new to
this development model and unsure of "what is the next step" on this.
I look forwards to learning, thanks,
Alex
--
Alexander Haley, Computer Scientist, 781-774-5156
Medical Information Technology, Inc.
Mailstop: F4E16W, MEDITECH Circle, Westwood, MA 02090
Re: xml output changed - relative paths now appearing?
Posted by Alexander Haley <ah...@meditech.com>.
> It's fixed on trunk:
>
> http://subversion.tigris.org/issues/show_bug.cgi?id=4398
>
>
Sweet! Thanks a lot!
--
Alexander Haley, Computer Scientist, 781-774-5156
Medical Information Technology, Inc.
Mailstop: F4E16W, MEDITECH Circle, Westwood, MA 02090
Re: xml output changed - relative paths now appearing?
Posted by Alexander Haley <ah...@meditech.com>.
> It's fixed on trunk:
>
> http://subversion.tigris.org/issues/show_bug.cgi?id=4398
>
>
Sweet! Thanks a lot!
--
Alexander Haley, Computer Scientist, 781-774-5156
Medical Information Technology, Inc.
Mailstop: F4E16W, MEDITECH Circle, Westwood, MA 02090
Re: xml output changed - relative paths now appearing?
Posted by Philip Martin <ph...@wandisco.com>.
Alexander Haley <ah...@meditech.com> writes:
> On Tue, Jul 16, 2013 at 6:26 AM, Bert Huijben <be...@qqmail.nl> wrote:
>
>> > -----Original Message-----
>> > With 1.7 I get
>> >
>> > <target
>> > path="/home/pm/sw/subversion/obj/wc">
>> > <entry
>> > path="/home/pm/sw/subversion/obj/wc/foo">
>> >
>> > while with 1.8 I get
>> >
>> > <target
>> > path="/home/pm/sw/subversion/obj/wc">
>> > <entry
>> > path=".">
>>
>> This appears wrong to me.
>> svn status always gave the paths in the same form as how the user passed
>> them, in both non-xml and xml form.
>>
>> I would guess that a lot of scripts break down if the paths don't match the
>> form that they expected from all previous versions.
>>
>> I think we should revert to the old form, where the input path dictates the
>> form in which we provide paths. Certainly for the --xml option, any other
>> form will break scripts.
>>
>
> So - where does this stand - having an informal list agreement that this
> is an issue - should I be submitting an issue formally- consider me new to
> this development model and unsure of "what is the next step" on this.
It's fixed on trunk:
http://subversion.tigris.org/issues/show_bug.cgi?id=4398
--
Philip Martin | Subversion Committer
WANdisco | Non-Stop Data
Re: xml output changed - relative paths now appearing?
Posted by Philip Martin <ph...@wandisco.com>.
Alexander Haley <ah...@meditech.com> writes:
> On Tue, Jul 16, 2013 at 6:26 AM, Bert Huijben <be...@qqmail.nl> wrote:
>
>> > -----Original Message-----
>> > With 1.7 I get
>> >
>> > <target
>> > path="/home/pm/sw/subversion/obj/wc">
>> > <entry
>> > path="/home/pm/sw/subversion/obj/wc/foo">
>> >
>> > while with 1.8 I get
>> >
>> > <target
>> > path="/home/pm/sw/subversion/obj/wc">
>> > <entry
>> > path=".">
>>
>> This appears wrong to me.
>> svn status always gave the paths in the same form as how the user passed
>> them, in both non-xml and xml form.
>>
>> I would guess that a lot of scripts break down if the paths don't match the
>> form that they expected from all previous versions.
>>
>> I think we should revert to the old form, where the input path dictates the
>> form in which we provide paths. Certainly for the --xml option, any other
>> form will break scripts.
>>
>
> So - where does this stand - having an informal list agreement that this
> is an issue - should I be submitting an issue formally- consider me new to
> this development model and unsure of "what is the next step" on this.
It's fixed on trunk:
http://subversion.tigris.org/issues/show_bug.cgi?id=4398
--
Philip Martin | Subversion Committer
WANdisco | Non-Stop Data