From: "Ludovic Courtès" <ludo@gnu.org>
To: Lars-Dominik Braun <ldb@leibniz-psychology.org>
Cc: 38541@debbugs.gnu.org
Subject: [bug#38541] [PATCH] ssh: Add Kerberos-support to ssh:// daemon URLs
Date: Mon, 16 Dec 2019 11:12:59 +0100 [thread overview]
Message-ID: <87eex4k28k.fsf@gnu.org> (raw)
In-Reply-To: <20191216071520.GA29716@zpidnp36> (Lars-Dominik Braun's message of "Mon, 16 Dec 2019 08:15:21 +0100")
Hi,
Lars-Dominik Braun <ldb@leibniz-psychology.org> skribis:
>> Nice! (Note that we normally list all the modified files/entities in
>> the commit log; see
>> <https://guix.gnu.org/manual/en/html_node/Submitting-Patches.html>.)
> oh, ok, I guess that includes the .texi and .patch files as well then:
>
> * doc/guix.texi: Document requirements for SSH-based connection to guix-daemon
> * gnu/packages/patches/guile-ssh-gssapi.patch: Add GSSAPI user authentication
> method to guile-ssh
Yes, more specifically:
* doc/guix.texi (The Store): Document requirements for SSH-based
connection to guix-daemon.
* gnu/packages/patches/guile-ssh-gssapi.patch: New file.
Documentation of the patch should go to the first lines of the patch.
>> Do you know if a Guile-SSH release is coming? If so, we could wait and
>> avoid carrying the Guile-SSH patch.
> I don’t know.
OK, let’s see…
Ludo’.
next prev parent reply other threads:[~2019-12-16 10:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 8:37 [bug#38541] [PATCH] ssh: Add Kerberos-support to ssh:// daemon URLs Lars-Dominik Braun
2019-12-14 23:33 ` Ludovic Courtès
2019-12-16 7:15 ` Lars-Dominik Braun
2019-12-16 10:12 ` Ludovic Courtès [this message]
2019-12-16 10:17 ` [bug#38541] Guile-SSH release? Ludovic Courtès
2019-12-17 17:42 ` Artyom Poptsov
2019-12-18 14:50 ` Ludovic Courtès
2020-02-19 12:52 ` [bug#38541] [PATCH] ssh: Add Kerberos-support to ssh:// daemon URLs Lars-Dominik Braun
2020-02-20 10:23 ` bug#38541: " Ludovic Courtès
2020-02-20 11:39 ` [bug#38541] " Lars-Dominik Braun
2020-02-21 23:37 ` Ludovic Courtès
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=87eex4k28k.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=38541@debbugs.gnu.org \
--cc=ldb@leibniz-psychology.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.