On Jan 26, 2011, at 12:19, Daniel Shahaf wrote:
> Ryan Schmidt wrote on Wed, Jan 26, 2011 at 09:12:44 -0600:
>> If I am in a subdirectory of that working copy and I commit,
>> svn-commit.tmp is created in the parent directory. For example, if
>> I am in /path/to/wc/foo/bar and I commit, svn-commit.
On Jan 26, 2011, at 12:21, Daniel Shahaf wrote:
> Ryan Schmidt wrote on Wed, Jan 26, 2011 at 09:12:44 -0600:
>> Note I did all tests with apr 1.4.2 and apr-util 1.3.10. Perhaps this
>
> Just curious, why mix apr/apr-util of different minor (1.%d) versions?
These are the current versions availab
On Wed, Jan 26, 2011 at 08:21:12PM +0200, Daniel Shahaf wrote:
> Ryan Schmidt wrote on Wed, Jan 26, 2011 at 09:12:44 -0600:
> > Note I did all tests with apr 1.4.2 and apr-util 1.3.10. Perhaps this
>
> Just curious, why mix apr/apr-util of different minor (1.%d) versions?
There is no apr-util 1.4
Ryan Schmidt wrote on Wed, Jan 26, 2011 at 09:12:44 -0600:
> Note I did all tests with apr 1.4.2 and apr-util 1.3.10. Perhaps this
Just curious, why mix apr/apr-util of different minor (1.%d) versions?
> is an apr or apr-util issue and trying earlier versions of those would
> produce different re
Ryan Schmidt wrote on Wed, Jan 26, 2011 at 09:12:44 -0600:
> If I am in a subdirectory of that working copy and I commit,
> svn-commit.tmp is created in the parent directory. For example, if
> I am in /path/to/wc/foo/bar and I commit, svn-commit.tmp is created in
> /path/to/wc/foo.
The directory o
On Jan 26, 2011, at 05:07, Stefan Sperling wrote:
> On Tue, Jan 25, 2011 at 08:28:08PM -0600, Ryan Schmidt wrote:
>>
I _know_, by sheer evidence of the svn-commit.tmp file being
"physically" there, that it is created one directory level above where
it was used to be created!
>>
On Tue, Jan 25, 2011 at 08:28:08PM -0600, Ryan Schmidt wrote:
>
> >> I _know_, by sheer evidence of the svn-commit.tmp file being
> >> "physically" there, that it is created one directory level above where
> >> it was used to be created!
> >
>
> FWIW, on my Mac OS X installation (Mac OS X 10
Daniel Shahaf wrote:
What version did you upgrade to 1.6.15 from?
From a 1.6.4 installation.
Are there any svn-commit.tmp, svn-commit.2.tmp preexisting?
No, there are none. I double checked and deleted all *.tmp in the
concerned directories.
What happens if you use the following script
Daniel Shahaf wrote:
BTW, with gvim you may have to use 'gvim -f' as your editor.
Besides totally not being the point: That is simply wrong. GVim.exe does
not require that parameter. And hasn't for years.
Greeting,
Andreas
Daniel Shahaf wrote:
BTW, with gvim you may have to use 'gvim -f' as your editor.
Besides totally not being the point: That is simply wrong. GVim.exe does
not require that parameter. And hasn't for years.
Greeting,
Andreas
Well, if you wish:
What i did is quite simple. I upgraded my subversion installation and
committing stopped working as it used to do.
I _know_, by sheer evidence of the svn-commit.tmp file being
"physically" there, that it is created one directory level above where
it was used to be created!
>> I _know_, by sheer evidence of the svn-commit.tmp file being
>> "physically" there, that it is created one directory level above where
>> it was used to be created!
>
FWIW, on my Mac OS X installation (Mac OS X 10.6.6, SVN 1.6.15), I also notice
the svn-commit.tmp is created one director
What version did you upgrade to 1.6.15 from?
Are there any svn-commit.tmp, svn-commit.2.tmp preexisting?
What happens if you use the following script as your editor:
#!/bin/sh
echo "hi" > $1
Andreas Wolff wrote on Wed, Jan 26, 2011 at 00:10:13 +0100:
> Well, if you wish:
>
> Wha
It's quite relevant actually, but I won't bother arguing that point.
Andreas Wolff wrote on Wed, Jan 26, 2011 at 00:12:27 +0100:
> Daniel Shahaf wrote:
>> BTW, with gvim you may have to use 'gvim -f' as your editor.
>
> Besides totally not being the point: That is simply wrong. GVim.exe does
> n
BTW, with gvim you may have to use 'gvim -f' as your editor.
You haven't actually stated what IS happening, just what you THINK is
happening. (Most of your assumptions regarding what should/shouldn't be
in cwd are wrong.)
The short answer is, svn runs 'gvim /path/to/file' and then reads
/path/to/file. The cwd isn't involved.
Feel free to follow up with m
16 matches
Mail list logo
