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

AW: [Subclipse-dev] enhancement to show history of genealogy in sublicpse

From: Amiri Arash OSF SD <Arash.Amiri_at_s-itsolutions.at>
Date: Tue, 1 Apr 2008 17:11:14 +0200

we have some assumptions in place. meaning that, we expect projects to have a certain structure. the "root" folder of the project must be right above the trunk folder. So, we assume a structure like:


this way, we find one of those three folders and take the parent folder from there. We then checkout everything from the repository from there (or, if we already checked out something and created the cache- and indexfile, we update the files, by comparing the revision numbers)

we expect projects in our company to be structured like that. otherwise, of course, we cant really provide the right history (the user will be notified through a messagebox that the structure provided does not allow the extended history to work). maybe this is really ugly, but we had no better idea.


-----Ursprüngliche Nachricht-----
Von: Mark Phippard [mailto:markphip_at_gmail.com]
Gesendet: Dienstag, 01. April 2008 15:31
An: dev_at_subclipse.tigris.org
Cc: Amiri Arash OSF SD
Betreff: Re: [Subclipse-dev] enhancement to show history of genealogy in sublicpse [bayes]

On Tue, Apr 1, 2008 at 9:24 AM, Amiri Arash OSF SD
<Arash.Amiri_at_s-itsolutions.at> wrote:

> We created an enhancement for subclipse in order to show the history of
> a file including all its branches and tags (and how they evolve).
> Our fix is based on cache files that are created for (eclipse) projects
> the first time the user tries to view the "enhanced" history. The cache
> files store relevant revisions for the given project including revision
> numbers and the changed paths. An index file points to the revisions in
> the cache file.
> Our algorithm first searches backwards to find the ultimate ancestor (as
> the current history view is doing right now, as long as "stop on copy"
> is not checked) and then searches forward and recognizes all copies and
> collects all relevant revisions.

I do not see how this can work. If I have my "trunk" project checked
out, nothing in its history will show that it was copied to create
branch or tags. The only way to see that is to look at the history of
those items, and the only way to know that they even exist is to look
at the entire history of the repository.

> If you are interested we could share the code with you (although it is
> not super cleanly programmed). we could just send you the plugin and the
> source and you might have a look at it. That would be great for us.

Some examples might be nice. Checkout some common open source
projects (for example the Subversion source code) and show what it
looks like.

Mark Phippard
To unsubscribe, e-mail: dev-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: dev-help_at_subclipse.tigris.org
Received on 2008-04-01 17:11:29 CEST

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