On May 5, 2016, at 4:12 PM, webster.br...@rogers.com wrote:
>
> From: Branko Čibej
>
>> Not 'status' -- 'svn status' should always show what 'svn commit' will
>> send to the server. But 'diff', I agree, could be smarter. For example,
>> right now, 'svn diff --summarize -x -w' will mention files
Hi,
I have a question about the behavior of svn checkout. Here is the scenario:
I have a standard trunk, branches, tags structure for one of my apps in a repo
and I created a branch, say at revision 500 of trunk.
Later, I delete the branch and the recreate another branch with the same name
and a
Hi,
I use svn and git in different projects. I've learned that if I place
*.f90 diff=fortran
in ~/.config/git/attributes, then git diff shows fortran
subroutine/function names
in the hunk headers. I'm trying to get similar functionality for svn diff.
I see that there is a svn option -x -p for C f
Hi,
this is in reference to a user reported problem on the TSVN mailing list [1]
The user is having an issue with using TSVN 1.9.4 over a Java-SSL-Tunnel
when trying to lock hundreds or thousands of files. The same operation
works without problems when:
- using TSVN 1.8.12 or
- using the SVN
Hi Brandon,
you can load older dumps into newer versions. So there should be no
reason to upgrade prior to the migration.
The only thing I'd consider is to upgrade the server to 1.6.23, since
1.6.11 is rather outdated on the 1.6 branch and therefore there might be
bugs in the dump logic whic
Hi,
you might wanna repost your question in English. I'm not sure whether
anybody here can read Chinese (if it is Chinese, that is).
All I can make out of this report is that you seem to get some error
running svnsync which seems to be a rather old version (1.7.4). If you
want/need to stick wi