git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH] git-svn: Avoid systematic prompt for client certificate when using "git svn branch"

From
MVMonard Vong <travelingsoul86@gmail.com>
Date
Jul 24, 2014, 16:25 UTC
Message-ID
<1406219159-4644-1-git-send-email-travelingsoul86@gmail.com>
In-Reply-To
<254135>

When a client certificate is required to connect to a Subversion repository, the certificate location and password may be stored in Subversion config directory. Commands like "git svn init/fetch/dcommit" do not prompt for client certificate/password if the location is set in SVN config file, but "git svn branch" does not use the config directory, resulting in prompting for certificate location/password all the time.

Build instance of SVN::Client in branch_cmd() with SVN config directory option instead of authentication baton. SVN::Client then builds its own authentication baton using information from the config directory.

Signed-off-by: Monard Vong <travelingsoul86@gmail.com>
---
 git-svn.perl | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/git-svn.perl b/git-svn.perl
index 0a32372..1f41ee1 100755
--- a/git-svn.perl
+++ b/git-svn.perl
@@ -1161,7 +1161,9 @@ sub cmd_branch {
 	::_req_svn();
 
 	my $ctx = SVN::Client->new(
-		auth    => Git::SVN::Ra::_auth_providers(),
+		config => SVN::Core::config_get_config(
+			$Git::SVN::Ra::config_dir
+		),
 		log_msg => sub {
 			${ $_[0] } = defined $_message
 				? $_message
-- 
1.9.3
Next: Eric Wong
Message 1 of 3 in “git-svn: Avoid systematic prompt for client certificate when using "git svn branch"”
  1. git-svn: Avoid systematic prompt for client certificate when using "git svn branch"Monard Vong, Jul 24, 2014
  2. Eric WongAug 2, 2014
  3. Monard VongAug 2, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.