Mailing-List: contact users-help@subversion.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (nike.apache.org: domain of lesmikesell@gmail.com
 designates 209.85.220.182 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <OFDEE87D75.DE719E7E-ON88257BC7.00738060-88257BC7.00757BB9@rockwellcollins.com>
References: 
 <OFF155594E.21E036B5-ON88257BC2.007E8623-88257BC2.007F0B83@rockwellcollins.com>
	<OF8FFE4458.71A17B48-ON88257BC3.007AC148-88257BC3.007CBBEE@rockwellcollins.com>
	<CAB84uBU4UJqXV3A9POHucLq4V6Eq9GNvQgfTLBnd20LL8fXRUA@mail.gmail.com>
	<CADkdwvQwW2YiMs0wv5khpmXndqN-1iS2gsUTj=9eX=htdKhovg@mail.gmail.com>
	<OF90D89D49.DE6A46A3-ON88257BC7.00593C11-88257BC7.005C59B1@rockwellcollins.com>
	<CAOAgVpxPN6iGxWTGzeUkAg8v3NNA2gi24fZt-or6kRrh_eV5gw@mail.gmail.com>
	<OFACEAFF91.6C153F9C-ON88257BC7.0061F8C6-88257BC7.00642543@rockwellcollins.com>
	<OF0D541C73.2F69F9D2-ON86257BC7.006553D1-86257BC7.0067B4C5@LocalDomain>
	<OFD66E75A7.68AF0CA6-ON88257BC7.00682D53-88257BC7.0068BF0C@rockwellcollins.com>
	<CAOAgVpxRMbT4odtwfnVQaEygOE3+TxpzUP8xfLRz3b1ykS_6Kw@mail.gmail.com>
	<OFDEE87D75.DE719E7E-ON88257BC7.00738060-88257BC7.00757BB9@rockwellcollins.com>
Date: Wed, 14 Aug 2013 16:49:38 -0500
Message-ID: 
 <CAOAgVpwoevspt6jPk_f-A=guagiM1jaQm5fsBAEFY+aCO64+Uw@mail.gmail.com>
Subject: Re: How to change paths on an external file without a full update
 --depth infinity?
From: Les Mikesell <lesmikesell@gmail.com>
To: dlellis@rockwellcollins.com
Cc: Ben Reser <breser@apache.org>, Ivan Zhakov <ivan@visualsvn.com>,
	Johan Corveleyn <jcorvel@gmail.com>, kmradke@rockwellcollins.com,
	"users@subversion.apache.org" <users@subversion.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Aug 14, 2013 at 4:23 PM,  <dlellis@rockwellcollins.com> wrote:
>
> Now, in our case, we do stuff for aircraft,... wouldn't it be nice to
> maintain living pedigrees with all similar models of aircraft?  Fix an issue
> in one place and advertise it to all the others.  File externals give you
> this.  It fits very well into the embedded safety critical world in the
> "don't touch that code unless you have to" and "let's fix it once".
> Refactoring code in this world just can't happen as often as you'd like (its
> also a chance to reinject bugs).
>
> Hope this helps!

So the point is to intentionally pull the HEAD revision of a whole
bunch of files together where each is located arbitrarily  and can
change independently?   I guess that's about the opposite of the way I
think of version control, so I can't suggest anything else.   Are
there enough different 'top level' collections or a fast enough change
that you can't simply copy the right files into place instead of
having external references there?

-- 
   Les Mikesell
    lesmikesell@gmail.com