Hi,
Since we work with externals a lot I would appreciate if diffing
changes in externals would be kept easily accessible in a way.
Kind regards,
Gunter.
Gunter Königsmann
R&D
Tel: +49 911-6559-6025
Fax: +49 911-6559-776747
www.semikron.com
gunter.koenigsmann_at_semikron.com
SEMIKRON Elektronik GmbH & Co. KG
Sigmundstrasse 200, 90431 Nürnberg, Germany
Amtsgericht Nürnberg HRA 13650
Komplementär:
SEMIKRON Elektronik Verwaltungs GmbH
Amtsgericht Nürnberg HRB 21338
Geschäftsführer:
Thomas Dippold
Peter Frey
Harald Jäger
>>> Friedrich Brunzema <brunzefb_at_yahoo.com> 24.06.2013 16:36 >>>
Hi,
a colleague just pointed this "annoying" behavior out. He has the
following:
File, Rev 1000 - base version of file
File, Rev 1001 - added an svn property to the file
File, Rev 1002 - changed an svn property of the file
File, Rev 1003 - feature change for file.
Now he does a SVN log which shows
1003
1002
1001
1000
My friend now selects 1003, and 1000 and does a "compare revisions"
TSVN now does the diff, launching a bunch of instances of TMerge, some
of which have the properties. The last compare TMerge window shows the
code (but I still have to close the property change windows, which in
99% of the time I am not interested in - at least not when reviewing
code).
With a tabbed external diff tool, the behavior is similar, except that
tabs are created - Bcompare (in my instance) then shows the first tab
(Prop window), second tab (prop window), third tab (code changes).
I propose adding way having a way to disable the properties diff during
a log. Don't know how best to do this on the UI level, simplest would
be (1) to do this only on with <Ctrl+Shift>, but this has its problems,
notably lack of visibility. One could add a global option (2) (in the
Diff viewer page) adding a "none" or "ignore" radio button. Finally, one
could add a checkbox to the log dialog (3) ("Ignore property diffs") -
but that would take extra screen real-estate and I'm not sure this is an
option I want to see everytime I see the log dialog. Personally, I
think (2) is the best option.
A workaround is to create a No-Op .exe [A program that does nothing]
and assign it as the program used for comparing revision of properties,
but this too is hacky - but it works with existing versions of TSVN.
Let me know what you think,
Friedrich
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=3058939
To unsubscribe from this discussion, e-mail:
[dev-unsubscribe_at_tortoisesvn.tigris.org].
IMPORTANT NOTICE - The contents of this email and attachments are
confidential. If you are not the intended recipient you must not use,
copy, distribute or rely on this email and should please return it
immediately or notify us by telephone. While we take every reasonable
precaution to screen out computer viruses from emails, attachments to
this email may contain such viruses. We cannot accept liability for loss
or damage resulting from such viruses. The integrity of email across
the Internet cannot be guaranteed and SEMIKRON will not accept liability
for any claims arising as a result of the use of this medium for
transmissions by or to SEMIKRON.
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
______________________________________________________________________
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=3058999
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-06-25 17:02:20 CEST