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

Re: [PATCH 1/2] Add password parameter to git svn commands and use it when provided instead of defaulting to end-user prompt

From
EWEric Wong <normalperson@yhbt.net>
Date
Oct 14, 2013, 18:40 UTC
Message-ID
<20131014184005.GA3352@dcvr.yhbt.net>
In-Reply-To
<20131014141127.GA21200@google.com>
Jonathan Nieder <jrnieder@gmail.com> wrote:
Show 13 quoted lines
> Hi,
> 
> arnaud.brejeon@gmail.com wrote:
> 
> > Signed-off-by: Arnaud Brejeon <arnaud.brejeon <at> gmail.com>
> 
> Thanks.
> 
> Can you say a little more about the context?  Do you run a script that
> wants to pass a password to 'git svn', do you type it each time on the
> command line, or something else?  Is it ok that the password would
> show up in "ps" output?  Would the platform's keyring or netrc be
> usable here, or is there something in the context that avoids that?

I think using keyring or netrc is more appropriate. Having a password on the command-line and visible to all via ps doesn't seem like something git should support.

Previous: Jonathan NiederNext: Jeff King
Message 4 of 9 in “Add password parameter to git svn commands and use it when provided instead of defaulting to end-user prompt”
  1. 1/2 Add password parameter to git svn commands and use it when provided instead of defaulting to end-user promptarnaud.brejeon@gmail.com, Oct 12, 2013
  2. 2/2 Add SVN trust-server-cert parameter to git svn to accept SSL server certificates from unknwon authorities without promptingarnaud.brejeon@gmail.com, Oct 12, 2013
  3. Jonathan NiederOct 14, 2013
  4. Eric WongOct 14, 2013
  5. Jeff KingOct 14, 2013
  6. Eric WongOct 14, 2013
  7. arnaud brejeonOct 15, 2013
  8. arnaud brejeonOct 21, 2013
  9. Jeff KingOct 25, 2013

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.