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

Re: [Subclipse-dev] revision graph: shouldnt it be possible to also show the merge lines?

From: jcompagner <jcompagner_at_gmail.com>
Date: Mon, 9 Feb 2009 17:41:26 +0100

ahh ok

Refresh revision info doesnt really say to me that it will get merge
information. What does it exactly refresh besides merge? Also the commit
comment and so on (because most stuff is static/fixed right?)

Multi select a few revision and then tell it to refresh would be nice then,
i dont have to have it for everything.

I guess it is logical that you have to do it on the revision that is merged
to? Merged from doesnt know anything i guess? (i first tried that and
nothing happened)

johan

On Mon, Feb 9, 2009 at 17:31, Mark Phippard <markphip_at_gmail.com> wrote:

> On Mon, Feb 9, 2009 at 11:28 AM, jcompagner <jcompagner_at_gmail.com> wrote:
>
> > i am just wondering this. now you see the trunk and the branch and when
> they
> > are created
> > But not for example the merge from branch to trunk of a fix. Shouldnt
> this
> > info be in the merge properties?
>
> It is explained here:
>
> http://subclipse.tigris.org/graph.html
>
> In summary, the performance is not good enough to simply include it.
> You can selectively add that information to a graph and it will then
> be persisted and remembered.
>
> --
> Thanks
>
> Mark Phippard
> http://markphip.blogspot.com/
>
> ------------------------------------------------------
>
> http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1043&dsMessageId=1129637
>
> To unsubscribe from this discussion, e-mail: [
> dev-unsubscribe_at_subclipse.tigris.org].
>

------------------------------------------------------
http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1043&dsMessageId=1129659

To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_subclipse.tigris.org].
Received on 2009-02-09 17:41:38 CET

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

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