wc-ng: Storing conflict information on the victim: trials and pitfalls

2010-10-26 Thread Hyrum K. Wright
This mail is part 2 in a series regarding the conflict information storage (see [1] for part 1). The current Plan (as denoted in both wc-metadata.sql and the conflict-storage notes) is to store conflict information in the ACTUAL node. This works fine (and is currently being done on trunk), but

Re: svn commit: r1024394 - /subversion/site/publish/packages.html

2010-10-26 Thread Hyrum K. Wright
[ This is going to come off rather biased, given my affiliations, so I'd appreciate some additional comments. ] From http://www.collab.net/downloads/subversion/redhat.html, I noticed that CollabNet only offers downloads of CollabNet Subversion Edge for Centos and Suse, but not vanilla Subversion

Re: svn commit: r1024394 - /subversion/site/publish/packages.html

2010-10-26 Thread Mark Phippard
We have always supported CentOS, I simply had not noticed that you had added a section for it. Given that anyone that uses CentOS knows that it is a clone of Red Hat it seems redundant to even have that section and I would be in favor of removing it entirely. The answer for SuSE is more