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

[Feature request] Commit dialog crazy idea(s) to make life easier

From: Oto BREZINA <otik_at_printflow.eu>
Date: Fri, 22 Apr 2011 10:22:43 +0200

Dear Stefan,
here are some ideas how make life with TSVN easier for me.

1. add "commit and return".
We have change sets, there may be more files where do different commits
is better. in all this cases this would help.
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2713604
Idea: can be separate button prefered or check box.
Idea: In smart way return only if not comited changed exists

1a. return to commit on all errors by default
Often my weak WL connection get lost without my notice. I lost not only
message which is too click far, but also file list. Many times folder I
use to start commit is closed, so I have to find it once again.

Update: reading
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2408318
I found that "Tortoise SVN most unknown features" may be good to have :)

2. add "create patch"
I remmeber times when Diff on directories was possible (?). Now this is
implemented as Check for modification.
I Use commit dialog as Diff(shows all changed files). I use this also
when creating patch is intended as it is one click closer (adding create
patch to one level up would make context menu biger).
Idea: Patch file may contain log message. I affraid this is not
supported by diff format easily. On receiver side applying patch would
lead to open commit dialog with message filled.

3. Show status if local WC revision matches servers one.
Some small icon/message can inform if:
  - Server is unreachable, thus commit would probably fail
  - Server connected but login not stored
    - on click enter creditials
  - Server have newer revision than newest in tree selected for commit
    - on click update WC or Check for modification
  - WC is rev mixed
    - on click update WC or Check for modification

Final Idea: Adding check boxes to Check for modification would solve
those. In our usual commit process Author of change call paired
programmer to revise changes. They go thru file list and may decide not
to commit some file. Then continue to check next ... Using CTRL to
select multiple items works, but is not preserved when double click is
used to open file.
Open all files on start with T-Merge don't work either as once file
processed to decrease mess you would close T-Merge window. Then you may
need to return to check that file and you are in same situation like before.
Also as selection will preserve error on commit making it less painful.
So add column selected for action. And buttons Commit, apply patch would
be nice too.

On other side. Check for modification would be just "log message" far to
commit dialog.
Disadvanage may be quite complex commit dialog for newbies.

Could be good for 1.8 TSVN

-- 
Oto BREZINA, Printflow s.r.o., EU
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2722414
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-04-22 10:23:03 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.