Randomly Intermittent Thoughts » Windows

How do you ‘svn delete’ missing working copy files?

nblom — Fri, 15 Oct 2010 18:27:25 +0000

Recently, I was upgrading a set of files in a svn working copy directory. I received the upgraded files from a third party. I used a merge tool to synchronize and merge the files, deleting files that were no longer needed. But this just deleted them from the working copy; not the svn repository. I could do a 'svn status' and "see" that files were missing, but there didn't seem to be a way for me to tell svn to delete them.

A quick Google Search pointed me to SNIPPLR.

The batch file created by troy, helped enormously!
I modified it a bit to fit my system. See below.

PLAIN TEXT

@echo off
rem :: This script deletes files from svn that are missing in the specified working copy.
set SVN=\bin\svn.exe
if "%1"=="" (
echo usage: %0 workingCopy
exit /b
)
for /f "usebackq tokens=1*" %%a in (`%SVN% status %1`) do (
if "%%a"=="!" (
echo svn delete "%%b"
%SVN% delete "%%b"
)
)

Edit: Fixed a problem with the actual svn delete command. It wasn't wrapped in %s so it was actually calling a SVN executable in my path. I recently had to replace a hard drive so when I went to run this batch file, svn wasn't in this new system's path and failed.

Yet Another Reason to Love Process Explorer — Part 2

nblom — Fri, 12 Oct 2007 20:27:46 +0000

This is a bit different from my last post about Process Explorer. Process Explorer is so powerful that I accidentally killed a different process than I wanted. This wasn't through some fancy schmancy search with regular expressions and kill accident. I just highlighted a process and clicked the .

I then proceeded to click 'Yes' on the simple dialog: .

Notice the blackened out word at the end of the Dialog's text? Well that is essentially what my brain did when I read that dialog.

So, long story short I killed the wrong process. Nothing seemed to break for a few hours. Then when I went to debug a couple of things, I wasn't able to connect to a service that was supposed to be running. I restarted somethings on my end, then remembered, "Oh yeah, I killed a random process earlier." I restarted the killed service and lo and behold everything started working again.

Lesson learned here kids: Don't kill random processes and then wonder why stuff breaks!

Process Explorer is part of the Microsoft Sysinternals set of utilities.

Yet Another Reason to Love Process Explorer — Part 1

nblom — Mon, 08 Oct 2007 15:26:41 +0000

Well, I just found another reason to love Process Explorer here: How To Identify What Programs Started svchost.exe in Windows.

This article describes how to use the command line and/or Process Explorer to find out what the hell svchost.exe is doing.

Open a command prompt and enter:

tasklist /svc /FI "IMAGENAME eq svchost.exe"

The above command will list all the svchost.exe processes and display the programs (DLL's) that have been started by svchost.exe.

Process Explorer is part of the Microsoft Sysinternals set of utilities.

Hopefully, this will become a series of posts. We'll see!