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

RE: Re: Tortoise SVN Command Line Small Feature Request

From: David Hetherington <djhreg_at_yahoo.com>
Date: Sun, 11 Nov 2012 09:39:27 -0800 (PST)

> On 2012-10-20 00:31, David Hetherington wrote:
> > Summary: It would be very helpful to have an option for :COMMIT like "/leave_if_nothing_to_do"
> >
> > - - -
> >
> > Background: We are making great use of subversion and Tortoise SVN. My company (AssatePress.com) is an extreme "Everything in the cloud" startup company. We don't even have wires to our office - our wireless LAN is provided by a 4G modem from Clear that links to a tower 350 meters away from one of our office windows.
> >
> > At any rate, we have ~50GB under subversion management on a Godaddy.com hosted server and use Tortoise SVN in the office to access it...802.11G to 4G to Internet to server.
> >
> > As a result, we have realized that it is a bit painful to have to re-checkout working copies if projects get large. So... we have developed a project naming convention and split our information into lots of small projects. That works great, but in practice it means that all day you are jumping between projects updating things here and there... it can be easy to forget to commit something.
> >
> > Not a problem: we write a little CMD file that invokes the Tortoise SVN command line to do a commit for all 40 or so projects. You then click through "cancelling" the ones with nothing to commit and properly commenting the ones that do.
> >
> > This approach works great except that it is a little tedious clicking through all 40 to find the 7 or 8 you changed during the day. Also, as you are sitting there repetitively clicking "cancel" (The windows all end up stacked exactly on top of each other, so it isn't too hard) it is easy to accidentally click "cancel" for something that actually needs to be committed.
> >
> > I tried using the /closeonend switch, but it does not have quite the desired effect. It only automates the close of things that do need committing after entering the comments and clicking "OK"
> >
> > What would be nice is a "/leave_if_nothing_to_do"
> > switch that would automatically close the 35 projects that don't have anything needed to be committed so I could simply focus on the things that need an update...
> >
> > In principle, I could checkout the source base, study the code and figure out how to implement this myself. But I am up to my eyeballs with my real work. Besides, I guess someone fully up to speed on the code could implement this in minutes...where I would need a week or two... (?)
> If you have batch to open all those commit window try to use SubWcRev to
> check for modification. Open commit only if it find some modification.
> Not sure if it detect all modification, but worthy to start with.
> http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-subwcrev.html
> More common way is to use overlay icons to visually check what WCs are
> changed and invoke commit only for those.
> --
> Oto


That worked perfectly. I simply modified my little batch file to read as follows:

SubWCRev %1 -n
If ERRORLEVEL 7 Start TortoiseProc.exe /command:commit /path:"%1" /logmsg:"Need to comment what changed"

(This is enclosed in a larger batch file that calls the smaller one once for each project. Makes it easy to maintain as projects are added and deleted)

Now it finds only the projects with modifications and pops up the window so I can examine what needs to be checked in.

For other comments:

1) The Windows UI integration is very elegant. I like it a lot. However, I have found that the modification status indicator is only about 70% reliable. Often there will be a project with a green check that actually has modifications outstanding.

2) Why am I checking in so many things to so many projects? Several reasons. As I mentioned above, we are not only managing text source code, but checking in large numbers of video and image objects as well. We have found that the projects get huge very quickly and have had to do a lot of partitioning to keep the size of individual projects manageable. Also, since I run the whole company (not just the programming operation) we are stretching the application of SVN a bit and making it the standard means for archiving ALL information for the company, not just source code. Currently I have 62 projects, about 50 GB on the server, and growing rapidly...

Thanks again for the help!

David Hetherington
Asatte Press


To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-11-11 18:43:58 CET

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.