Re: [Subclipse-users] Switch after branch

On Dec 6, 2007 4:31 PM, Linus Tolke <linus@tigris.org> wrote:

> If I check the "Switch working copy to new branch/tag" while creating a new
> branch, I notice that the "breadcrum", i.e. the update of the subclipse:tags
> property of the project ends up in the branch and not in the trunk.
>
> This is not very convenient since the features provided by the
> subclipse:tags does not work:
> * It is not possible to look at the history and see where the branch was
> made.
> * It is not possible for my collaborating friends to quickly find the branch
> and switch to it.
>
> Hence-forth I will recommend to my developer group that we don't use the
> "Switch working copy to new branch/tag" but instead leave it unchecked,
> commit in the main branch, and then switch.
>
> Is this taken care of by an issue or should I file it? Issue 471 has some
> similar reasoning but that is not expressed as a problem.

Well, it would be taken care of by issue 471, but I do not expect that
issue to be done. I'd suggest filing another issue. There are two
things we could possibly do:

1) Do not expose that checkbox if the subclipse:tags property is set
on the item you are branching.

2) If we leave the checkbox, and the user checks it, do not do the
subclipse:tags processing after creating the branch.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org