Return-Path: Delivered-To: apmail-infrastructure-dev-archive@minotaur.apache.org Received: (qmail 8267 invoked from network); 9 Jun 2009 20:44:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 9 Jun 2009 20:44:27 -0000 Received: (qmail 13074 invoked by uid 500); 9 Jun 2009 20:44:38 -0000 Delivered-To: apmail-infrastructure-dev-archive@apache.org Received: (qmail 12967 invoked by uid 500); 9 Jun 2009 20:44:38 -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 12957 invoked by uid 99); 9 Jun 2009 20:44:38 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Jun 2009 20:44:38 +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.216 as permitted sender) Received: from [209.85.218.216] (HELO mail-bw0-f216.google.com) (209.85.218.216) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Jun 2009 20:44:29 +0000 Received: by bwz12 with SMTP id 12so300048bwz.17 for ; Tue, 09 Jun 2009 13:44:09 -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=muY49lyQO6KwYdUGX9CIpoPBXNtcYb6OeRdoY3LPdQ0=; b=HO/SQINuIsAklog/dS5EKf4k4V44hPqcOxCByxWjA8f2mwRle3YvDNamM8YAv6+vWx R79Itg3vYCcBloUxZ8WQUGjmj2v9Fwc55jCYU9EzZ43ZjAWRHLHINpNWzXmyb37+Uhsv 5esDi1BGSghIeD0JMQ/8xV1WBU6DYc22g3rYg= 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=DmqUwP3cNdhhtvTqfOPjUw9B+d9akp1fNRB2Rrl0lfFfnbam3W29eCaU6/9hVTEzTF Ug7z9Xw8pM6dgaOjKY46wlXYeiXB3No/cje6Se/LY7iXoB5KYbZW3WfX4ZKSfnLU3yTj i5YmmEr8XlMGEaCVQ3dnJ8TKQ6ZtEU8U+n/vw= MIME-Version: 1.0 Received: by 10.204.124.10 with SMTP id s10mr506657bkr.34.1244580249130; Tue, 09 Jun 2009 13:44:09 -0700 (PDT) In-Reply-To: <1244570660.7402.17.camel@localhost> References: <4A28C562.20504@chatka.org> <510143ac0906060212w64ba060ci4d7c53a98dd363@mail.gmail.com> <4A2A42BA.1010503@apache.org> <510143ac0906061409y5e62e1b1kbe92d6afc96d9520@mail.gmail.com> <4A2B6A4A.5010300@chatka.org> <4A2E73D0.8030007@apache.org> <1244570660.7402.17.camel@localhost> From: Jukka Zitting Date: Tue, 9 Jun 2009 22:43:49 +0200 Message-ID: <510143ac0906091343j48b906a4t415eb3d79679c798@mail.gmail.com> Subject: Re: Servicemix git repository To: infrastructure-dev@apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi, On Tue, Jun 9, 2009 at 8:04 PM, Santiago Gala wrote: > If there is a semi-automated way to get the bunch of repos I might try > to merge them into one big "all-in-one" repo, for people to experiment. > Depending on results, either approach is valid It might be an interesting exercise, but I'd rather keep the mapping between svn and git as simple and straightforward as possible. If the ServiceMix people think it's a good idea to have just a single repository, they could move all their code into a single svn trunk. But I'm sure there's a good reason to keep all those codebases separate. BR, Jukka Zitting