Return-Path: Delivered-To: apmail-infrastructure-dev-archive@locus.apache.org Received: (qmail 62612 invoked from network); 28 Feb 2008 01:53:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 28 Feb 2008 01:53:19 -0000 Received: (qmail 96815 invoked by uid 500); 28 Feb 2008 01:53:14 -0000 Delivered-To: apmail-infrastructure-dev-archive@apache.org Received: (qmail 96748 invoked by uid 500); 28 Feb 2008 01:53:14 -0000 Mailing-List: contact infrastructure-dev-help@apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: infrastructure-dev@apache.org Delivered-To: mailing list infrastructure-dev@apache.org Received: (qmail 96739 invoked by uid 99); 28 Feb 2008 01:53:14 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Feb 2008 17:53:14 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jukka.zitting@gmail.com designates 209.85.200.175 as permitted sender) Received: from [209.85.200.175] (HELO wf-out-1314.google.com) (209.85.200.175) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Feb 2008 01:52:29 +0000 Received: by wf-out-1314.google.com with SMTP id 27so3047321wfd.26 for ; Wed, 27 Feb 2008 17:52:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=THxjFUSrFEPoKno5iTSSlxITr76icJy8HjT91gPIxrc=; b=ASJI71RC4Y8HAjDhbLwANDacOuerrcXVQi76XSp1I9YScTBGwCzBRiNSbofQ8cGV7gJ44bHfV1uSE5yhOQ8eKCe0yIlMn70olIyg6yTW/ogBurVpmUZMejPSskZcztIxnlwcIqRGC6tKgJKMIhhlvqpZw5EQXtH1LeLDRFm+oqg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=QwH/oaJJwCOBCkHyqQQBjwJg7kgkKya6y1sxeSmSRv0ZJ8jSw0Sxm8NAkcorE02DzlOxwDJZElhC8e+L24yhTM1IQlANXwOvtvIzvo18N/E585aywLP4x43ENYztus+X+Dg2jshB0RpfLUkZZQDW92rE5fygE2Te/3oi1u7NG6U= Received: by 10.142.49.4 with SMTP id w4mr5972913wfw.185.1204163569917; Wed, 27 Feb 2008 17:52:49 -0800 (PST) Received: by 10.142.213.16 with HTTP; Wed, 27 Feb 2008 17:52:49 -0800 (PST) Message-ID: <510143ac0802271752id7b8a8ajc481f7b0cce59067@mail.gmail.com> Date: Thu, 28 Feb 2008 03:52:49 +0200 From: "Jukka Zitting" To: infrastructure-dev@apache.org Subject: Re: [scm] Advanced version control at Apache In-Reply-To: <510143ac0802270219s738d8407v77ac15c5e98fc78e@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <510143ac0802270219s738d8407v77ac15c5e98fc78e@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org Hi, On Wed, Feb 27, 2008 at 12:19 PM, Jukka Zitting wrote: > I'd like us to start collecting use cases that our current version > control infrastructure doesn't support out-of-the-box. Just to avoid any misunderstandings: The reason many of the use cases discussed point out at least some lack of functionality in Subversion is just because we're only talking about cases that aren't supported by default. Thus by definition all the use cases discussed reach beyond the current (known) capabilities of Subversion. There are a number of features in Subversion and supporting tools like IDE integrations that enable use cases that would be impossible to support with many other current SCM systems. But since I'm taking Subversion for granted, I won't be raising such use cases as issues. So, even though we might at times sound critical of Subversion, pointing out one lack of functionality after another, this is only because of the systematic skew mentioned above. BR, Jukka Zitting