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

Re: (maybe) some new features

From: Greywolf <greywolf_at_starwolf.com>
Date: Mon, 28 Sep 2009 13:15:39 -0700 (PDT)

[Thus spake Rafael M. Heise ("RMH: ") Yesterday...]

RMH: 1. Temporary local files. I don't know about you all guys, but
RMH: sometimes I just create some temporary files and these files are only
RMH: local files. I don't want commit these files and I don't want to add
RMH: these files on ignore-list and submit that. These files are only
RMH: temporary, e.g specific configuration files created to test a
RMH: software. I need keep these files for a long time, while I'm coding
RMH: and waiting for a answer from the customer. These files appears on the
RMH: commit file list and I can't add these files in the ignore-on-commit
RMH: list just because these files are not versioned. So, I have thinking
RMH: about and I would suggest to allow adds these files (not versioned) on
RMH: the ignore-on-commit list.

This is odd news to me; my dialog only shows me versioned files, with the
"Show Unversioned Files" checkbox. Once I uncheck it it seems to stay
unchecked (which is the desired behaviour!), and I have no problems with
committing just the versioned stuff.

If there is nothing to commit, I am asked if I want to see unversioned
files. Sweet 'n' easy, no big deal at all. I don't know what's going
wrong on your end.

RMH: 2. Sometime ago I had a situation where I were coding and the other
RMH: developer needs to compile the project. But a commit made by me don't
RMH: allowed him to compile the project. My commit needs some changes on
RMH: database and on that moment the customer couldn't do the changes. So,
RMH: we decided to "update to revision", but we would like to "update to
RMH: revision" only the files modified in the specific revision (the
RMH: revision commited by me). I tried to do that on "Log Dialog", but I
RMH: only could "update to revision" if I "update to revision" all files
RMH: modified from HEAD until the specific revision. As I said, I only
RMH: wanted "update to revision" a few files, not all files. I can do it if
RMH: I "update to revision" file by file. I would suggest to add a new
RMH: feature on "Log Dialog" to allow "update to revision" only the files
RMH: selected or only the files modified in a specific revision. I know,
RMH: maybe these files was changed after, and couldn't compile if I undo
RMH: the modifications. But I think when someone "update to revision"
RMH: somefile, this person know what could happens. I only "update to
RMH: revision" when I know what I want. To me, "update to revision" is not
RMH: an habitual task.

I keep "update to revision" on my top-level menu because there are just
enough times where I want to only update to a certain rev. Granted, most
times, the "certain rev" is HEAD :). If you can adjust your thinking to
see that "update to rHEAD" == "update", you'll never bother with plain
old "update" again.

No real big deal, here; why not just put "update to revision" on your
top level menu, put "update" down on the cascading menu, and then you
can select your files in the explorer window, then right-click and update
to revision rBLAH? If your files are scattered all over the place, you'll
have to do multiple invocations of this, but still, it's possible.

As far as only files modified in a specific revision: Open the log and go
to that specific revision. The bottom pane will contain a list of files
at that revision. I believe there is a way to make use of this.

Best of luck,

                                --*greywolf;

--
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2401389
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-09-28 22:16:21 CEST

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

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