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

RE: Working copy format regression in 1.5.x branch and probably trunk

From: Bert Huijben <bert_at_vmoo.com>
Date: Tue, 19 Feb 2008 12:03:32 +0100

> -----Original Message-----
> From: Branko Čibej <brane_at_xbc.nu> [mailto:=?ISO-8859-
> 2?Q?Branko_=C8ibej_<brane_at_xbc.nu>?=]
> Sent: dinsdag 19 februari 2008 11:25
> To: Bert Huijben
> Cc: dev_at_subversion.tigris.org
> Subject: Re: Working copy format regression in 1.5.x branch and
> probably trunk
>
> Bert Huijben wrote:
> > Hi,
> >
> > While trying to apply the ankhsvn/NSvn test suite on my new SharpSvn
> > library I found a regression in the working copy parsing.
>
> This was so long ago I actually forgot that I made this change. :)
>
> -----------------------------------------------------------------------
> -
> r7711 | brane | 2003-11-12 08:41:50 +0100 (Wed, 12 Nov 2003) | 6 lines
>
> Use "" instead of "svn:this_dir" in the entries file.
>
> * subversion/include/svn_wc.h (SVN_WC_ENTRIES_THIS_DIR): Define to "".
> * subversion/libsvn_wc/entries.c (svn_wc__atts_to_entry): It the
> entry name is "svn:this_dir", change it to SVN_WC_ENTRIES_THIS_DIR.

The zipped working copy in the testcase has format 2. When subversion 1.0 was released the wc format used was 4. I will fix the issue by updating the zip as this is technically not a bug in subversion, but only an implementation change since 1.4. (Only 1.0++ compatibility is guaranteed)

I don't think I need to open an issue on this one.

--- snip subversion/libsvn_wc/wc.h ---
 * The change from 3 to 4 was the renaming of the magic "svn:this_dir"
 * entry name to "".
--- snip ---

        Bert

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-02-19 12:03:45 CET

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

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