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

Re: Making revision graphs easier to read

From: Simon Large <simon.tortoisesvn_at_googlemail.com>
Date: Fri, 5 Sep 2008 09:05:27 +0100

2008/9/4 Stefan Küng <tortoisesvn_at_gmail.com>:
> nmgeek wrote:
>> 8. It would be really helpful to show an additional node above the
>> head
>> node when the file is modified in the working copy.
> Above the head? Your working copy can't be above the HEAD.

I think he means local modifications in the working copy. However I
don't think that is a good idea for a couple of reasons:

1. It only works when invoked for a working copy, otherwise the rev
graph won't know where to look for changes. That might cause the
unwary to believe that there are no changes, when in fact they have
called the rev graph from the repo browser, or from another branch.
2. It means a WC crawl which could take a long time for a large WC.
3. Your local changes may not be against HEAD anyway. Others may have
committed changes since you last updated.

>> I have a process question: When you or Simon answer with
>> something like "good point" should I interpret that as, "yeah
>> I'll improve the documentation so this is addressed" or is it
>> up to me to file an issue against the documentation to help insure
>> its addressed in the documentation.
> Yes. That means that we think it's a good idea and will
> implement/improve/... that feature. It does not mean that we file an
> issue for it though.
> Speaking for myself: I usually move such mails to a special folder in my
> mail client. Whenever I have time I go through that folder and pick some
> task to do. Sometimes however if I start working on a task and then
> realize that either the feature is not good or that it's not possible to
> implement it (e.g., some API doesn't return the required info), then I
> just drop it - but that doesn't happen often.

In gmail I star any emails that indicate changes I need to make to the
docs. I did have an open documentation issue for 1.5, but starring the
emails is easier. If someone else wants to contribute I can go back to
using the issue tracker to make it easier to share.

Thanks for your comments Glenn, well thought through feedback is
always appreciated.


: ___
: oo // \\ "De Chelonian Mobile"
: (_,\/ \_/ \ TortoiseSVN
: \ \_/_\_/> The coolest Interface to (Sub)Version Control
: /_/ \_\ http://tortoisesvn.net
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-09-05 10:05:40 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.