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

New update output comments

From: Oto BREZINA <otik_at_printflow.eu>
Date: Tue, 10 Jul 2012 03:50:14 +0200

While I like idea about reduced update output of external, I don't like
implementation that much.
Here are some idea about how it can be improved. Still may need some
polishing trough.

1. If there is modification in external, only updated(mereged ...) file
name is shown with some indentation. This indentation however accumulate
over WCs(on multi WC update) and after few WCs if may shift name out of
screen. It do move Action too what I don't see as necessary.

2. It shows only WC base not External - this is perfectly fine. Except I
sometimes mess information about revision of External, but not a big issue.

3. Line
External starting external appears only once in multi WCs update.

I would like to suggest little bit different solution.

A. If there is NO modification from update process on WC. Output only
one line.
Done WcRoot at revision:%x

On update start line:
Actualization WcRoot
would be shown and later changed to final one.

same would happen with other finals like Skiped.

B. If there ARE modifiactions lines output would be line:
Actualization WcRoot
Done at revision: %x

C. I don't see reason for Note lines at all ...

D. In case of external
indentation does not seems to be needed. They does not help much as
order of external makes it useless.
If possible it can be replaced with bold for WC/external base path.

X. After update you cas see some over result:
Skiped: 9, Updated: 179 ....
Can be this updated on the fly. Expecialy handling conflict this way
seems be better then have after every even OK WC message about conflict.
In fast it makes searching for conflict harder as there are many "false"
red lines.

To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-07-10 03:50:33 CEST

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

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