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

Re: [Subclipse-users] What is Tags column on Resource History used for?

From: Mark Phippard <markp_at_softlanding.com>
Date: 2006-03-15 17:28:10 CET

Eugene Kuleshov <eu@md.pp.ru> wrote on 03/15/2006 11:16:26 AM:

> Mark Phippard wrote:
> > See: http://subclipse.tigris.org/branch_tag.html
> >
> Mark, can you please update this page and add step by step
> instructions how to create and commit new branch.
>
> I could be wrong, but I seems that this custom editing dialog is more
> oriented for already existing branches and it is unclear how to use it
> to add info for branch that is being created, so that versioned property

> will be part of the branch.

When you make the branch, properties are copied with the branch. But
generally when creating a branch, the property would be set on the source
of the branch. So you would not need to add any new info into the branch
itself. You are adding it in the place where the branch came from. This
is the missing breadcrumb that Subversion does not create.

The custom editing dialog exists for maintaining the info. Whether it is
adding in historical info from an existing repository, or adding new info
about new branches. However, if the branch is created from Subclipse then
there are cases where the property will be auto maintained.

Mark

_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Wed Mar 15 17:28:23 2006

This is an archived mail posted to the Subclipse Users mailing list.

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