Re: [Subclipse-users] What is Tags column on Resource History used for?
From: Mark Phippard <markp_at_softlanding.com>
Date: 2006-03-15 20:06:38 CET
Eugene Kuleshov <email@example.com> wrote on 03/15/2006 01:45:46 PM:
> Mark Phippard wrote:
No, you are already wrong. If you are working locally, and the item you
> 1) If I choose "HEAD revision in repository" in tag/branch dialog, then
The property would never go into the target of the copy. Or rather, what
> >> Also it does not work when you need
You got me. I wanted to make sure this feature was difficult. It had
> > Should we have not added the feature? Is
We knew before the feature was implemented that it had to be a hack.
> > What don't you get here? The property is not set on the tagged copy
-- > > EVER. It is set on the SOURCE of the tagged copy. If you make a tag from > > trunk, then trunk needs the property, not the tag. > > I perfectly get everything. What you don't get is that such common > scenario is really purely explained in documentation. It doesn't seem like you get it. You still seem to be hung up on the property being set in the tag itself which does not happen. > >> I think it is quite common use case that been asked several times in > >> this mail list. I'd say it is worth a FAQ entry... > > > > I do not know what would be an FAQ entry, and this is one of the first > > conversations I can ever remember happening since this feature was > > implemented. Hardly anyone has ever even mentioned the feature, despite > > several people begging for it for months. > > Question to answer is this: "I have working set of 10 projects that > need to be tagged/branched at the same time. How do I do that in Subclipse?" Do they have a common parent? If so, I do it from the repositories view so I can tag all 10 at once. I then manually edit the tags property for the 10 projects. Otherwise, you can create the tag folder in the repositories view and then take the Create Branch/Tag option 10 times. Once for each project. This will update the property automatically, although it still needs to be committed. > Also, I may not understand how that property is working, but from > what I've seen, tag/branch copy has been created and then tag info > property is changed/added into head revision. Kind of strange to do such > thing in head revision after tagging. This kind of behavior is not > explained anywhere in Subclipse documentation and I am basically asking > to fix that. Get it started. Rough out a patch. Read the web page again, I think it is explained. > BTW, you should learn from Subversive plugin. It has really > interesting approach to tagging... If I could get it to work long enough, I might try. Mark _____________________________________________________________________________ Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs. _____________________________________________________________________________ --------------------------------------------------------------------- To unsubscribe, e-mail: firstname.lastname@example.org For additional commands, e-mail: email@example.comReceived on Wed Mar 15 20:06:57 2006
This is an archived mail posted to the Subclipse Users mailing list.