From: Jelle Licht <jlicht@fsfe.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>,
Ioannis Panagiotis Koutsidis <gk.ppp7@gmail.com>
Subject: Re: GSoC update
Date: Wed, 11 Jul 2018 16:26:54 +0200 [thread overview]
Message-ID: <CAPsKtfJ6uZ0P_iVM4cM_erqV_aofJ-HYEWa-e0otsfWb893pBw@mail.gmail.com> (raw)
In-Reply-To: <87zhyyogtx.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 2630 bytes --]
2018-07-11 0:40 GMT+02:00 Ludovic Courtès <ludo@gnu.org>:
> Hi Ioannis,
>
> Ioannis Panagiotis Koutsidis <gk.ppp7@gmail.com> skribis:
>
> > This patch adds initial support for .socket unit files. It does not
> > currently work but is near completion.
>
> Could you expound a bit? That’s a very short summary for all the sweat
> you’ve put in it. :-)
>
> Also, what is the patch against? It’s not against ‘master’; I suppose
> it’s against the previous state of your own branch, do you have a copy
> of your repo on-line?
>
> > During the past month I also worked on a patch that adds signalfd and
> > fiber support but these are currently way too unstable and for that
> > reason I have not included them in this patch.
>
> It’s OK that the thing doesn’t quite work—we knew it was not an easy
> task. What’s disappointing though is that you didn’t come to us to
> discuss the issues until now. GSoC is not about working in all
> loneliness separately from the rest of the group; it’s about becoming
> part of the group.
>
> On IRC Jelle and I (and possibly others) offered help on the ‘signalfd’
> issue; I also outlined reasonable milestones (first, only use
> signalfd(2) instead of SIGCHLD, then discuss together what it would take
> to Fiberize the whole thing.) It’s sad that you remained stuck instead
> of taking this opportunity to discuss it with us.
>
Ioannis, could you perhaps share some of your w.i.p. code regarding
signalfd-based signal handling in guile? Adding to what Ludo'
mentioned, I imagine you are running into some peculiarities regarding
guile's way of handling signals, so I would recommend to start
lurking on #guile if you did not do this before now, so you can interact
with the folks with the most expertise regarding the problems you
might be facing :-)
>
> > From cd260ae65056b53749e7c03f2498a28af2525934 Mon Sep 17 00:00:00 2001
> > From: Ioannis Panagiotis Koutsidis <ixk680@student.bham.ac.uk>
> > Date: Tue, 10 Jul 2018 20:03:21 +0300
> > Subject: [PATCH] .socket units
> >
> > ---
> > modules/shepherd.scm | 44 +++--
> > modules/shepherd/service.scm | 170 ++++++++++-------
> > modules/shepherd/systemd.scm | 354 ++++++++++++++++++++++++-----------
> > 3 files changed, 368 insertions(+), 200 deletions(-)
>
> The patch changes lots of things and unfortunately, without
> explanations, I do not understand what to do with it. Like what’s the
> new feature? How is it used? What implementation choices were made?
> What’s left to be done?…
>
> Thank you,
> Ludo’.
>
>
[-- Attachment #2: Type: text/html, Size: 3445 bytes --]
next prev parent reply other threads:[~2018-07-11 14:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-10 17:42 GSoC update Ioannis Panagiotis Koutsidis
2018-07-10 22:40 ` Ludovic Courtès
2018-07-11 14:26 ` Jelle Licht [this message]
2018-07-12 12:13 ` Ioannis Panagiotis Koutsidis
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=CAPsKtfJ6uZ0P_iVM4cM_erqV_aofJ-HYEWa-e0otsfWb893pBw@mail.gmail.com \
--to=jlicht@fsfe.org \
--cc=gk.ppp7@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.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 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).