On my W2K system it is C:\Documents and Settings\williams\Application
On W2K and XP, the "Documents and Settings" is a system folder in the system
partition. Under this folder is a sub-folder for each user account on the
What would XML give you in this case that INI cannot? Using XML would be
overkill for such a simple file.
----- Original Message -----
From: "Ray Johnson" <Rayj@ingenio.com>
Sent: Wednesday, April 14, 2004 11:05 AM
Subject: System-wide config file for Windows
Ok - this is perhaps a dumb question but i can't for he life of me
figure it out and the docs are not really helping me out.
I want to set the global-ignores file to know about additional files to
ignore. We do *not* want to use the Windows registry. Much easier for
our Ops guys to back up and edit a file then poking around in the
registry. Shouldn't be a problem as the docs state you can use an INI
file to set this stuff up. But where the heck is the location of that
The book simply states this:
"...on Windows machines, it again looks for a Subversion directory
inside the common Application Data location (again, as specified by the
Windows Registry). Unlike the per-user case, the svn program does not
attempt to create the system-wide configuration area."
What the heck is the "common Application Data location"? Since svn
apparently doesn't attempt to create the system-wide configuration area
am I supposed to keep guessing until I find it? I'm sure I must be
missing some clearer documentation somewhere. Can anyone help point me
in the right direction?
BTW, while pounding my head on this I have some other questions
1) Why isn't the config in an XML format? Even MS is (slowly) moving
away from the crappy registry and .INI world...
2) Can you not have a repository level config? For example, I may have
Linux code in one repository and Windows code in another. I would like
to set things like the editor-cmd differently based on repository.
However, it seems like I must do it for all repositories or have each
user set things up in user configs.
3) Can you override the diff-cmd somehow at the command line level? (I
didn't see a way to.) Most of our users want to use a visual diff tool.
However, we have some scripts in our build environment that obviously
can't use a GUI tool. If I could add an extra argument in my automated
scripts that would work...
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Wed Apr 14 03:15:08 2004