Return-Path: Delivered-To: apmail-infrastructure-dev-archive@minotaur.apache.org Received: (qmail 82234 invoked from network); 27 Apr 2009 08:13:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 27 Apr 2009 08:13:23 -0000 Received: (qmail 46302 invoked by uid 500); 27 Apr 2009 08:13:23 -0000 Delivered-To: apmail-infrastructure-dev-archive@apache.org Received: (qmail 46172 invoked by uid 500); 27 Apr 2009 08:13:22 -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 46161 invoked by uid 99); 27 Apr 2009 08:13:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Apr 2009 08:13:22 +0000 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.218.168 as permitted sender) Received: from [209.85.218.168] (HELO mail-bw0-f168.google.com) (209.85.218.168) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Apr 2009 08:13:14 +0000 Received: by bwz12 with SMTP id 12so2029323bwz.17 for ; Mon, 27 Apr 2009 01:12:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:content-type :content-transfer-encoding; bh=OoAMnjYXdXoeZeM+9WAMGxC4L84t/Kr10hRKI6rRubM=; b=b2f2tnOsntKcmDX9PpOgtO6JNcy/eOKTkL11m7mG+e0PLtxIAdcXzPh8rzhyaC/P7J JMlApnGVSj8Bfoan9C+bKHB0tgnwupZCcimVHSJ3x2NV51V5sXr6q+5FMmrm50lmu4jD lK+a9VB3TdCtdFsZbg96aXgTq1cOgDFjH4EfI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; b=wWdqHGPoTEo3MOsLp2bcJlaqr1kOtyVimop/W9cHq5cIzbmfonjifmmgIOMcKmSu1v qIgVGQKo7RzchnoZeAZ+fVNGy1bgjbUvScOUSvebwjouKvWH9mcMlT45pa0+vKWDxsUo pyNpewD8rglmQ3BjssiwAgQ+p9OwhTtwXz0Nc= MIME-Version: 1.0 Received: by 10.204.77.102 with SMTP id f38mr5061785bkk.65.1240819974167; Mon, 27 Apr 2009 01:12:54 -0700 (PDT) In-Reply-To: <4239a4320904262250g66fc8a3csda720e5a767d1b90@mail.gmail.com> References: <4239a4320904262250g66fc8a3csda720e5a767d1b90@mail.gmail.com> From: Jukka Zitting Date: Mon, 27 Apr 2009 10:12:39 +0200 Message-ID: <510143ac0904270112u4a96e571mab2b6822d147cac6@mail.gmail.com> Subject: Re: Status of Version Control at the ASF To: infrastructure-dev@apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Hi, Good summary! On Mon, Apr 27, 2009 at 7:50 AM, Paul Querna wrote: > =A0- Need to hear more about 'git-svn issues' =A0and better understand > how to integrate these work flows. The main issue ATM is the problem with dcommitting against svn.eu.apache.org. The svn mirroring delay is breaking the rebase that dcommit is trying to do right after committing pending changes. This is not critical as the operation can be restarted after a few seconds when the svn changes have been synced, but it still is quite annoying especially as it affects even single commits (I wouldn't mind having some pain associated with committing multiple changes in a single operation. :-). Would it be OK to allow git svn users to dcommit directly against svn-maste= r? Other practical problems I've faced are mostly related to svn:eol-style settings and such. Those are best handled on the git mailing list. BR, Jukka Zitting