git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dennis Kaarsemaker <dennis@kaarsemaker.net>
To: "Mantas Mikulėnas" <grawity@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] contrib: add credential helper for libsecret
Date: Mon, 10 Oct 2016 22:20:50 +0200	[thread overview]
Message-ID: <1476130850.7457.8.camel@kaarsemaker.net> (raw)
In-Reply-To: <20161009123417.147239-1-grawity@gmail.com>

On Sun, 2016-10-09 at 15:34 +0300, Mantas Mikulėnas wrote:
> This is based on the existing gnome-keyring helper, but instead of
> libgnome-keyring (which was specific to GNOME and is deprecated), it
> uses libsecret which can support other implementations of XDG Secret
> Service API.
> 
> Passes t0303-credential-external.sh.

When setting credential.helper to this helper, I get the following output:

$ git clone https://private-repo-url-removed private
Cloning into 'private'...
/home/dennis/code/git/contrib/credential/libsecret/ get: 1: /home/dennis/code/git/contrib/credential/libsecret/ get: /home/dennis/code/git/contrib/credential/libsecret/: Permission denied

Looks suboptimal. Am I holding it wrong?

D.

  parent reply	other threads:[~2016-10-10 20:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-09 12:34 [PATCH] contrib: add credential helper for libsecret Mantas Mikulėnas
2016-10-10 18:34 ` Jeff King
2016-10-10 20:20 ` Dennis Kaarsemaker [this message]
2016-10-10 20:46   ` Jeff King
2016-10-11 15:01     ` Dennis Kaarsemaker
2016-10-11 15:01 ` Dennis Kaarsemaker
2016-10-11 19:36   ` Junio C Hamano
2016-10-11 19:48     ` Mantas Mikulėnas
2016-10-11 19:59       ` Mantas Mikulėnas
2016-10-11 20:09       ` Dennis Kaarsemaker
2016-10-11 20:13         ` Junio C Hamano
2016-10-11 20:19           ` Junio C Hamano
2016-10-11 20:32           ` Dennis Kaarsemaker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1476130850.7457.8.camel@kaarsemaker.net \
    --to=dennis@kaarsemaker.net \
    --cc=git@vger.kernel.org \
    --cc=grawity@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).