Thanks for your prompt response Mark! Yes that new option sounds perfect.
Would you like me to enter the issue against the subclipse project or
just subversion itself?
Mark Phippard wrote:
> On 10/10/07, Tom Walter <walter.tom@gmail.com> wrote:
>
>> My company uses a ticketing system that involves creating a branch
>> matching the ticket number, that the QA department then tests before
>> merging to the trunk.
>>
>> I often find myself needing to branch a small subsection of a project in
>> a folder several levels deep in a heirarchy. It's simple enough to copy
>> that folder into another folder in SVN, however it's often handy to
>> preserve the entire directory structure leading to that folder as well,
>> so that QA can easily tell where the code needs to be merged, and also
>> because you might need to copy several folders from various places in
>> the heirarchy into your branch.
>>
>> This isn't so simple to achieve currently, I would have to manually
>> create my branch directory, and then each folder in the heirarchy within
>> it, before copying the relevant folder across. It would be neat if there
>> was an option in subclipse to recreate the heirarchy leading to the
>> subfolder you are branching.
>>
>> For example, this command currently fails because the t23974 folder
>> doesn't yet exist:
>> copy -rHEAD http://svn/trunk/www http://svn/branches/t23974/www
>> HTTP Path Not Found
>> svn: PROPFIND request failed on '/!svn/bc/32907/branches/t23974'
>> svn: '/!svn/bc/32907/branches/t23974' path not found
>>
>> It seems it wouldn't be too hard for subclipse to guess your intention
>> and create the t23974 directory before copying www to it. Of course,
>> sometimes you might have made a mistake, however that could be handled
>> with a 'The t23974 directory does not exist, would you like to create it
>> first?' confirmation.
>>
>> You might well say I should just copy from the root folder since copies
>> in SVN are virtually free anyway. And yes, in an ideal world that would
>> be fine. However the real world isn't so simple, and copying or
>> switching from the root in our case is a fairly painful experience due
>> to a proliferation of svn:externals throughout the heirarchy.
>>
>
> You are going to be happy with SVN 1.5 The svn copy command has a new
> --parents option that will create the missing parents automatically.
>
> I still need to figure out how I would expose this in Subclipse UI,
> but it'll be there.
>
> Please enter an issue though with your use case.
>
>
Received on Thu Oct 11 03:00:12 2007