From: Bengt Richter <bokr@bokr.com>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 44186@debbugs.gnu.org, divoplade <d@divoplade.fr>
Subject: bug#44186: Recursive mkdir
Date: Sat, 24 Oct 2020 01:32:14 +0200 [thread overview]
Message-ID: <20201023233214.GA13637@LionPure> (raw)
In-Reply-To: <CAJ3okZ3pvC=vyO6u-VT9Q9tM5voso=6A1kfJt3mP3z7jSY150A@mail.gmail.com>
Hi,
On +2020-10-24 00:07:19 +0200, zimoun wrote:
> Dear,
>
> On Sat, 24 Oct 2020 at 00:00, divoplade <d@divoplade.fr> wrote:
>
> > I have slightly modified the mkdir function so that it takes a third
> > argument to try to create the intermediate directories when calling
> > mkdir, in effect acting as "mkdir -p".
> >
> > However, I could not make the test suite run the ports test, on which I
> > added the test for the new behavior. Is it expected? How do I run it?
> >
> > In the mean time, here is the WIP version of the patch.
>
> [...]
>
> > > Otherwise, why is it not possible to send a patch to Guile?
>
> The discussion started here:
>
> <http://issues.guix.gnu.org/issue/44130>
>
> All the best,
> simon
>
>
>
An alternate solution could be programmed using ffi, as documented in [1], n'est-ce pas?
What would guix best-practice guidance say about that?
[1] info guile ffi
--
Regards,
Bengt Richter
next prev parent reply other threads:[~2020-10-23 23:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6ff632f5c1e378647cecc7177b7018fb8a0ee6d4.camel@divoplade.fr>
[not found] ` <86sga420pw.fsf@gmail.com>
2020-10-23 22:00 ` bug#44186: Recursive mkdir divoplade
2020-10-23 22:07 ` zimoun
2020-10-23 23:32 ` Bengt Richter [this message]
2020-10-24 6:17 ` divoplade
2020-10-25 4:13 ` Bengt Richter
2020-10-25 7:45 ` Ricardo Wurmus
2020-10-25 9:07 ` divoplade
2020-10-25 10:44 ` divoplade
[not found] ` <handler.44186.B.16034904223692.ack@debbugs.gnu.org>
2020-10-23 22:46 ` divoplade
2020-10-26 21:05 ` Leo Prikler
2020-10-27 7:01 ` divoplade
2020-10-27 9:19 ` Leo Prikler
2020-10-27 10:21 ` divoplade
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201023233214.GA13637@LionPure \
--to=bokr@bokr.com \
--cc=44186@debbugs.gnu.org \
--cc=d@divoplade.fr \
--cc=zimon.toutoune@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 read-only IMAP folder(s) and NNTP newsgroup(s).