> I reckon that anyone is able to cut-paste what is in that dialog, but that
> wasn't the them later (taking murphy's law into account , the only one needed will
> be forgotten), which is why a automatism comes into place.
> Regarding where the log should be saved, why not in the user's application data
> directory: C:\Documents and Settings\<USERNAME>\Application
> Data\TortoiseSVN ?
> I don't believe the save location would forcefully have to be configurable at start,
> but it would be a great idea.
> The log could be stored in .xml but I don't see where xml would be useful, text
> should do the trick , the rotation of the logfile could also be configurabe (as most
> application logs are) and its content too (being able to log
> commits/updates/checkouts independently could be useful, the commit log is always
> available from the standard log command for instance, and could be unselected by default).
> I am totally aware that the request is a bit vague, but as end-users, we can at best give you
> our input, but I believe that as tsvn devs, you have such a greater deal of experience with the
> product development that we do, that you sure are better at deciding those points.
> I hope this helps,
On 10/11/06, Stefan Küng <email@example.com> wrote:
Peter Scmsvn wrote:
> are there any tsvn devs that might have some insights on that remark ?
> Would it be possible to open a feature-addition ticket ?
Why would you need to log the actions? You can see them in the progress
dialog. If you need them for later, you can
Ctrl-A (to select all entries)
Open text editor
Ctrl-V (to paste the entries into the text editor)
Also, this request is incomplete as it doesn't answer the most basic
* where would that log be saved to?
* if the save location is configurable, what would be the default?
* what format should the log be? xml? Text? What should the entries look
* How long should the log be kept?
* Should the log be stored all in one folder, or in subfolders according
to the repository UUID?
I don't entirely see the usefulness (I understand the concept of maintaining a log I just don't know why someone would use it -- and, I'm not trying to be sarcastic, if someone could share a use it would be helpful) of this feature since we have the 'Check for modifications' dialog, and the log would really have no bearing/authority on what is currently in a working copy.
Another question to throw into the mix, what should happen when two working copies on a machine are connecting to the same repository?
Received on Wed Oct 11 22:59:20 2006