unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Cc: 25422@debbugs.gnu.org
Subject: bug#25422: [PATCH 0/2] Support single-entry search paths
Date: Mon, 23 Jan 2017 23:02:54 +0100	[thread overview]
Message-ID: <87bmuxmo35.fsf@gnu.org> (raw)
In-Reply-To: <idjmveiue0l.fsf@bimsb-sys02.mdc-berlin.net> (Ricardo Wurmus's message of "Mon, 23 Jan 2017 14:00:58 +0100")

Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> skribis:

> Ludovic Courtès <ludo@gnu.org> writes:
>
>> Hi!
>>
>> These patches for ‘core-updates’ add support for “single-entry” search
>> paths like ‘GIT_SSL_CAINFO’.  This is achieved by setting ‘separator’ to
>> #f in the search path spec.
>>
>> Feedback welcome!
>
> This looks good and will be useful for the Lua search path as well.

Thanks for your feedback.  I’ve pushed it as
fcd75bdbfa99d14363b905afbf914eec20e69df8.

Ludo’.

  reply	other threads:[~2017-01-23 22:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-11 20:36 bug#25422: GIT_SSL_CAINFO set incorrectly Leo Famulari
2017-01-14 21:20 ` Ludovic Courtès
2017-01-22 21:51   ` bug#25422: [PATCH 0/2] Support single-entry search paths Ludovic Courtès
2017-01-22 21:52     ` bug#25422: [PATCH 1/2] guix package: Honor the order of profiles when -p appears multiple times Ludovic Courtès
2017-01-22 21:52     ` bug#25422: [PATCH 2/2] search-paths: Allow specs with #f as their separator Ludovic Courtès
2017-01-23 13:00     ` bug#25422: [PATCH 0/2] Support single-entry search paths Ricardo Wurmus
2017-01-23 22:02       ` Ludovic Courtès [this message]
2017-04-02 22:22         ` Ludovic Courtès
2017-01-20  4:27 ` bug#25422: GIT_SSL_CAINFO set incorrectly Mekeor Melire
2017-01-23 13:57   ` Ludovic Courtès
2017-02-10 16:22     ` Mekeor Melire
2017-02-10 20:51       ` 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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87bmuxmo35.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=25422@debbugs.gnu.org \
    --cc=ricardo.wurmus@mdc-berlin.de \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).