> From: Les Mikesell <[email protected]> > To: BRM <[email protected]> > Cc: "[email protected]" <[email protected]> > Sent: Wednesday, February 27, 2013 5:49 PM > Subject: Re: Tagging svn:externals > > On Wed, Feb 27, 2013 at 4:44 PM, BRM <[email protected]> wrote: >>> >>> Won't work - it has to be committed somewhere or it won't be > built. >> >> Perhaps then you need a different tool. >> For example, git-svn[1] is might be what you want. >> >> When something is ready for QA it is pushed to a git repository for Jenkins > to pick up. >> How you change the externals in the process I'm not sure; but it would > at least give you >> a trackable repository that would mimick a modified working copy. >> >> Otherwise I think you're out of luck if you don't want to (i) > commit to trunk, or (ii) create a branch, >> but still want to track it in the repository somehow. > > No, I think the choices are to tag from the working copy or commit a > change after making the tag. But neither seem like the tool is > designed to do what I'd expect to be a common operation cleanly.
What do you mean? Branching from a working copy is extremely easy: $ svn copy . ^/path/to/tag/or/branch It's a first-class operation in subversion. Likewise, you can: $ svn copy . ^/path/to/tag/or/branch $ svn switch ^/path/to/tag/or/branch ...make modifications here.. $ svn commit Ben
