On 4/2/07, Zaphod Beeblebrox <[EMAIL PROTECTED]> wrote:
> Hmmm...I was thinking svn:externals was more for your working copy.
> With SVK, I set up a mirror of Rays svn in my svn (svk calls it a
> depot). Then I tell it to sync to my /trunk . Then I tell it to copy
> from /trunk to /local. Now, w
Yeah, svn:externals is a working-copy concept that allows you to have
your working copy split amongst several SVN destinations (and store
that configuration in SVN itself for easy maintenance and reuse). It
doesn't help you with local changes to the remote code (in fact, it
prevents that arrangeme
Hmmm...I was thinking svn:externals was more for your working copy.
With SVK, I set up a mirror of Rays svn in my svn (svk calls it a
depot). Then I tell it to sync to my /trunk . Then I tell it to copy
from /trunk to /local. Now, whenever I want to make changes to it, I
check out the local vers
Crazily enough, I've got almost the exact same situation as yerzelf.
SVN:externals. Love it. Live it. L-word it.
Using patch files is quite awesomely nifty too...
** *
Qs or Cs? Holla! :-P
On 4/2/07, Zaphod B wrote:
> I use the ever present BlogCFC for a couple of blogs. Ea
You need a vendor branch. There's a section in the book about how to
use them. It's not really any different from a "normal" branch, other
than the fact that you don't write any code on the branch, you import
it from the third party.
cheers,
barneyb
On 4/2/07, Zaphod Beeblebrox <[EMAIL PROTECTE
I use the ever present BlogCFC for a couple of blogs. Each blog has a
little bit different layout, but that's about it. I'm trying to
figure out how I could set up the Subversion repository and include
Ray's subversion repository to be something like this:
/trunk/(Ray's SVN - still updateable wh
6 matches
Mail list logo
