X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Message-ID: <d34314100810010618i3d781fe3w7570bcd7cf974d52@mail.gmail.com>
Date: Wed, 1 Oct 2008 16:18:22 +0300
From: techtonik <techtonik AT gmail DOT com>
To: cygwin AT cygwin DOT com
Subject: SVN mirrors and :externals
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Hello there,

I wonder what is the general attitude towards providing SVN mirrors
for maintained packages and about using SVN for maintenance itself?
In particular it would be interesting to know if SVN can simplify
maintenance of cygwin packages through svn:externals mechanism?
http://svnbook.red-bean.com/en/1.5/svn.advanced.externals.html

WBR,
-- 
--anatoly t.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/