All of lore.kernel.org
 help / color / mirror / Atom feed
From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: "BARDOT Jérôme" <bardot.jerome@gmail.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Jeff King <peff@peff.net>,
	git@vger.kernel.org
Subject: Re: Questions, improvements
Date: Thu, 21 Oct 2021 00:39:47 +0000	[thread overview]
Message-ID: <YXC20wWfiu0wHel/@camp.crustytoothpaste.net> (raw)
In-Reply-To: <9009a3af-9d21-cad1-6a4c-e1a81ece6f83@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 962 bytes --]

On 2021-10-20 at 12:40:10, BARDOT Jérôme wrote:
> On 20/10/2021 13:42, Johannes Schindelin wrote:
> > A quite complete, cross-platform credential helper (included in Git for
> > Windows and enabled by default, but it also works on macOS and on Linux)
> > is Git Credential Manager:
> > https://github.com/microsoft/Git-Credential-Manager-Core/
> 
> We only use GNU\Linux for our work, i see there is .deb, are they
> integrated in official debian repositories (stable) ?
> 
> We avoid tools not Libre and not package by default in debian. (with few
> exeptions) 

I believe this tool is open source, but it requires .NET Core, which is
not in Debian, so it's not included.  I don't know if it will work with
Mono instead, which is packaged in Debian.

I _think_ Debian prefers Mono over .NET Core because it is substantially
more portable in terms of architecture support.
-- 
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

  reply	other threads:[~2021-10-21  0:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-19 17:38 Questions, improvements BARDOT Jérôme
2021-10-19 21:31 ` Jeff King
2021-10-20 11:42   ` Johannes Schindelin
2021-10-20 12:40     ` BARDOT Jérôme
2021-10-21  0:39       ` brian m. carlson [this message]
2021-10-20 12:25   ` BARDOT Jérôme
2021-10-21  1:00     ` brian m. carlson

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=YXC20wWfiu0wHel/@camp.crustytoothpaste.net \
    --to=sandals@crustytoothpaste.net \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=bardot.jerome@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.