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

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

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Fri, 22 Apr 2011 21:42:08 +0200

On 22.04.2011 10:22, Oto BREZINA wrote:
> 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

The commit dialog is already very crowded. Would something like this
really be worth another checkbox or button?

>
> 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.

That should already work:
Settings dialog->General->dialogs 2->Reopen commit and branch/tag dialog
after a commit failed.

> 2. add "create patch"
> I remmeber times when Diff on directories was possible (?). Now this is
> implemented as Check for modification.

right-click on folder, choose "create patch", select all entries, click
ok. then click on "copy to clipboard" and the diff viewer will open.

> 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.

But when you create a patch, there's no place to enter a log message.
We'd have to add something like that to the "create patch" dialog.
And where would we store that log message after the patch got applied to
a working copy?

>
> 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

You mean overlay icons? There are no more spots left, so no more icons
there.

> 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.

Really? The checks are preserved for me when I double click on items.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2722829
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-04-22 21:42:14 CEST

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