From: Oliver Propst <oliver.propst@fripost.org>
To: Attila Lendvai <attila@lendvai.name>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: workflow while hacking on Shepherd
Date: Tue, 01 Mar 2022 11:20:52 +0100 [thread overview]
Message-ID: <70acf905fffd7b72c0799549b9824c2c@fripost.org> (raw)
In-Reply-To: <T7xRN1BEFUY894zRXI1yYB_Xwq5DIeWxpIlDLjtPF5TCYjmGrjc4cGoIqoYEG0RTmghutERgn9xF_Bd7C-FbLRnLPzmfyYhBnOIbGq7_0vU=@lendvai.name>
On 2022-03-01 08:59, Attila Lendvai wrote:
Hi Attlila thanks for working on this. For me your proposal seems to
make sense (but I guess input from more folks would be needed).
--
Kinds regards Oliver Propst
https://twitter.com/Opropst
next prev parent reply other threads:[~2022-03-01 10:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 7:59 workflow while hacking on Shepherd Attila Lendvai
2022-03-01 8:49 ` Maxime Devos
2022-03-02 13:22 ` Attila Lendvai
2022-03-01 10:20 ` Oliver Propst [this message]
2022-03-01 17:17 ` 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=70acf905fffd7b72c0799549b9824c2c@fripost.org \
--to=oliver.propst@fripost.org \
--cc=attila@lendvai.name \
--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 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).