It makes sense to me now.
Thank you Daniel.
-Original Message-
From: Daniel Shahaf [mailto:danie...@apache.org]
Sent: Monday, May 09, 2016 6:15 PM
To: Tati, Aslesh
Cc: users@subversion.apache.org
Subject: Re: Subversion checkout behavior at non-existent revision
Tati, Aslesh wrote on
Hello Stefan,
I've verified that the branch doesn't exist at revision 500 and only trunk has
revision 500.
I should have mentioned the subversion server and the client version in my
initial email. These are the server and the client versions that I'm using.
svnadmin --version
svnadmin, version
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
ing the value
of the 'store-plaintext-passwords' option to either 'yes' or 'no' in
'$HOME/.subversion/servers'.
-------
Store password unencrypted (yes/no)?
From: Tati, Aslesh [mailto
Hi,
Is it possible to store password when a subversion query is being done as a
different user.
Say I'm user foo and would like to run "svn log --username bar
https://"
I'm prompted for user bar's credentials and the command succeeds when bar is
successfully authenticated.
The next time foo
1. You can use svn merge --dry-run if you are using command line or if you
are using a client like tortoise then a test merge option should be available.
This won't actually merge but show if there will be any failure in case an
actual merge was performed.
2. Do the re-intergrate merge
I'm trying to setup a path based authorization using different LDAP groups.
Developers should be able to see all repositories and commit to all repos (the
corresponding LDAP group is subversion_developers)
Business users should be able to see all repositories but only commit to
specific assigne
