Personally, I'd like it to show the head of each branch as a node in the
graph. I'd much prefer being able to just select the branch revision or the
head nodes instead of using a right click option of "Compare head
revisions". Showing every revision though I think could be overkill.
- Jody
On 1/11/06, Matthew Janulewicz <Matthew.Janulewicz@nextestate.com> wrote:
>
> I agree (having been a ClearCase and Perforce admin in the past) that
> having the option to show all revisions in the graph would be neato. The
> graph (nice redesign, by the way!) does give a lot of useful
> information, but sometimes you really do want to see each submit, too. I
> think it would be cool to have it default to the way it is now, but
> maybe have a right click menu item that says 'gimme more info' that will
> build the whole, possibly huge, all-commits-including graph. The
> end-user would have to weigh the value of the graph vs the time it takes
> to construct, but it could be useful, that's for sure.
>
>
> -Matt
>
>
> -----Original Message-----
> From: Liam Friel [mailto:liam.friel@s3group.com]
> Sent: Wednesday, January 11, 2006 11:30 AM
> To: users@tortoisesvn.tigris.org
> Subject: RE: 1.3.0 RC1 or RC2 - no revision graph with SSH access
>
> I can see this is a philosophical argument in a sense, so I don't have a
> major problem with the way it is.
>
> I have just got somewhat used to the ClearCase graphical version tree
> for looking at revisions of a file.
>
> While you can make this show you all revisions on all branches ever,
> this is not the default because, as you rightly
> point out, on a significantly complex project this would be a huge
> forest of versions and branches all over the place
> and not always useful. It is, however, *sometimes* useful, so it is
> possible to do this.
>
> By default, it shows you the collapsed revision graph. This is the
> revision of the branch you are looking at, plus the
> latest versions on active branches, plus any previous versions which
> were created as a result of merges from other
> branches. Ccase reckons that versions which were created by merging from
> other branches are more "significant" than
> incremental versions on a branch.
>
> So this is I suppose quite close to what the revision graph in TSVN will
> show me ... Once I branch a file a few times,
> that is.
> Experiments continuing. I am not in any way knocking svn or TSVN at all,
> I am actively trying to figure out how to fit
> it into our current workflow.
>
> Thanks
> Liam
>
>
>
> The information contained in this e-mail and in any attachments is
> confidential and is designated solely for the attention of the intended
> recipient(s). If you are not an intended recipient, you must not use,
> disclose, copy, distribute or retain this e-mail or any part thereof. If
> you have received this e-mail in error, please notify the sender by
> return e-mail and delete all copies of this e-mail from your computer
> system(s).
> Please direct any additional queries to: communications@s3group.com.
> Thank You.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
> For additional commands, e-mail: users-help@tortoisesvn.tigris.org
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
> For additional commands, e-mail: users-help@tortoisesvn.tigris.org
>
>
Received on Wed Jan 11 22:31:42 2006