[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 <B.Huijben_at_competence.biz>
Date: Tue, 19 Feb 2008 16:25:36 +0100

To close this issue completely (and for future reference) I provide the following information:

> -----Original Message-----
> From: Bert Huijben [mailto:bert_at_vmoo.com]

> 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)

# svn log -v -r 21597 http://svn.collab.net/repos/svn/trunk/
------------------------------------------------------------------------
r21597 | philip | 2006-09-21 22:43:26 +0200 (do, 21 sep 2006) | 3 lines
Changed paths:
   M /trunk/subversion/libsvn_wc/entries.c

* subversion/libsvn_wc/entries.c
  (svn_wc__atts_to_entry): Remove obsolete "svn:this_dir" support.
------------------------------------------------------------------------

# svn diff -r 21596:21597 http://svn.collab.net/repos/svn/trunk/subversion/lib
svn_wc/entries.c
Index: entries.c
===================================================================
--- entries.c (revision 21596)
+++ entries.c (revision 21597)
@@ -469,12 +469,6 @@

   /* Find the name and set up the entry under that name. */
   name = apr_hash_get(atts, SVN_WC__ENTRY_ATTR_NAME, APR_HASH_KEY_STRING);
- /* XXX Replace the obsolete "svn:this_dir".
- XXX This code should go away by 1.0 */
- {
- if (name && strcmp(name, "svn:this_dir") == 0)
- name = SVN_WC_ENTRY_THIS_DIR;
- }
   entry->name = name ? apr_pstrdup(pool, name) : SVN_WC_ENTRY_THIS_DIR;

   /* Attempt to set revision (resolve_to_defaults may do it later, too) */

>
> Bert
Received on 2008-02-19 16:26:10 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.