On 25/10/05, Nikolaj Berntsen <knb@mobilepeople.dk> wrote:
> >
> >
> >>How do I find out which release tags relate to each revision of a file?
> >>
> >>
> >One possible and hopefully easy way of doing this, is by appending
> >revision number to each folder in the repository browser. That way you'd
> >see the revision number of each tag, and if you have the file in question
> >displayed in the history view at the same time, there'd be no problem
> >seeing which revision the file was at in each tag.
> >
> >
> Not sure if I get the question right, but I think that subversion, or
> subclipse(?), does something like this automatically.
>
> In your subclipse repository browser, select "someproject/tags/sometag"
> and choose revision history from the context menu. In that view, make
> sure that you have ticked "show selected paths". The copy operation will
> show as an "A" operation. The affected path is the tag you chose
> "someproject/tags/sometag", there will also be an autogenerated
> "description" saying something like "from someproject/trunk:revisionNo".
>
That is not quite what I want.
Given a particular file, I can easily find the modification history in
terms of revisions.
However, what I want to do (and was able to do in CVS) was to see in
the revision history which tags and releases applied to each revision.
The CVS History in Eclipse includes the following columns:
Revision | Tags | Date | Author | Comment
The Tags column automatically shows the release and branch tags.
By scanning the column, it's very easy to see what revision belongs to
each release, and to see where the file changed between releases.
This is vey helpful when trying to find where something broke, e.g. it
was working in release 1.9, but not in 2.1. And the reverse - which
was the minimum release to contain this fix?
Received on Wed Oct 26 03:29:14 2005