[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: vendor branch questions

From: Garrett Rooney <rooneg_at_electricjellyfish.net>
Date: 2002-07-22 02:07:27 CEST

On Sun, Jul 21, 2002 at 07:03:01PM -0500, Eric Gillespie wrote:
> Garrett Rooney <rooneg@electricjellyfish.net> writes:
> > so i've been playing around with recreating cvs's 'vendor branch'
> > functionality in svn this weekend, and i've got a few questions.
> This will answer at least some of your questions:
> http://hackers.progeny.com/~epg/svn-3rdparty.html

cool! perhaps something like this should be in the svn handbook...

> > (side question, is that the correct behavior? it sure confused me...)
> Yes. It confused me at first too.
> > the problem is that it's a pain in the ass to do it. what i'd like
> > would be for 'svn import' to be able to import from an unversioned
> > directory into my working copy, handling all the 'svn add' and 'svn
> > delete' stuff that's needed. or, i'd like 'svn diff' to be able to
> > show the diff between two paths that have no common ancestry, so i
> > could simply 'svn import' the new release onto my vendor branch and
> > have 'merge' and 'diff' work correctly.
> I'd prefer either of those, too. The process my document outlines
> isn't really difficult. Once you get used to it it's instinctive,
> and you just fly right through it.

oh, it doesn't strike me as all that bad, certainly not any worse than
cvs *grin*, but i still think we could make it easier. or at least we
could document the procedure somewhere more official ;-)


garrett rooney                    Remember, any design flaw you're 
rooneg@electricjellyfish.net      sufficiently snide about becomes  
http://electricjellyfish.net/     a feature.       -- Dan Sugalski
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 22 02:07:53 2002

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.