From: Jelle Licht <jlicht@fsfe.org>
To: Carlo Zancanaro <carlo@zancanaro.id.au>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Improving Shepherd
Date: Mon, 29 Jan 2018 23:27:54 +0100 [thread overview]
Message-ID: <CAPsKtfJRuZdxUZ6LtPMJpurnWjgEYZ6X6BdhaF1yeBFka+Eeww@mail.gmail.com> (raw)
In-Reply-To: <871si8bc5g.fsf@zancanaro.id.au>
[-- Attachment #1: Type: text/plain, Size: 785 bytes --]
2018-01-29 22:14 GMT+01:00 Carlo Zancanaro <carlo@zancanaro.id.au>:
> I'm keen to do some work on shepherd. Partially this is driven by me using
> it to manage my user session and having it not always work right, and
> partially this is driven by me grepping the code for "FIXME" (which was
> slightly overwhelming). If anyone is keen to chat about it on Friday,
> please find me! I have some ideas about things I'd like to do, but I don't
> really have any idea what I'm doing. Any help/advice/encouragement you can
> give me will be appreciated!
>
Count me in! I am currently not using GNU Shepherd for my user session yet,
but would like to collaborate on some future direction on making it more
easy to use.
I'll only be there after/around lunch though ;-).
>
> Carlo
>
- Jelle
[-- Attachment #2: Type: text/html, Size: 1376 bytes --]
next prev parent reply other threads:[~2018-01-29 22:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 21:14 Improving Shepherd Carlo Zancanaro
2018-01-29 22:27 ` Jelle Licht [this message]
2018-02-05 10:49 ` Carlo Zancanaro
2018-02-05 13:08 ` Ludovic Courtès
2018-02-05 15:56 ` Carlo Zancanaro
2018-02-09 13:26 ` Ludovic Courtès
2018-02-09 19:50 ` Carlo Zancanaro
2018-02-09 21:32 ` Christopher Lemmer Webber
2018-02-14 13:10 ` Ludovic Courtès
2018-02-15 13:55 ` Andy Wingo
2018-02-10 13:34 ` Jelle Licht
2018-02-14 13:25 ` Ludovic Courtès
2018-02-15 17:05 ` Jelle Licht
2018-02-15 19:04 ` Mark H Weaver
2018-02-05 16:00 ` Danny Milosavljevic
2018-02-05 16:41 ` Carlo Zancanaro
2018-02-09 13:22 ` Ludovic Courtès
2018-02-09 20:51 ` David Pirotte
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=CAPsKtfJRuZdxUZ6LtPMJpurnWjgEYZ6X6BdhaF1yeBFka+Eeww@mail.gmail.com \
--to=jlicht@fsfe.org \
--cc=carlo@zancanaro.id.au \
--cc=guix-devel@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 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.