all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mekeor Melire <mekeor@posteo.de>
To: "(" <paren@disroot.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH guix-artwork v2] website: posts: Add Dissecting Guix, Part 1: Derivations.
Date: Mon, 12 Dec 2022 20:59:11 +0000	[thread overview]
Message-ID: <874ju0tk0c.fsf@posteo.de> (raw)
In-Reply-To: <20221212193137.1264-1-paren@disroot.org>

2022-12-12 19:31 paren@disroot.org:

> This patch adds an updated blog post, taking the critiques on 
> this thread into
> account.
>
> * Changed post name to just "Derivations"
> * Removed subjective "simple" language
> * Added subheadings to "Exploring `<derivation>`"
> * Added field recap to "Conclusion"
> * Added "Utilising `<derivation>`", with examples for 
> READ-DERIVATION,
>   READ-DERIVATION-FROM-FILE, WRITE-DERIVATION, and 
>   BUILD-DERIVATION
> * Wrapped lines to 80 columns

looks good to me :)


  reply	other threads:[~2022-12-12 21:01 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-08 18:24 Dissecting Guix -- blog post series (
2022-12-09  7:31 ` 宋文武
2022-12-09  7:33   ` (
2022-12-09  9:32     ` bokr
2022-12-09 17:25       ` (
2022-12-12 13:46         ` Bengt Richter
2022-12-10 21:25 ` Mekeor Melire
2022-12-11 10:08   ` (
2022-12-12  1:43     ` Mekeor Melire
2022-12-12 17:26       ` (
2022-12-12 19:31 ` [PATCH guix-artwork v2] website: posts: Add Dissecting Guix, Part 1: Derivations (
2022-12-12 20:59   ` Mekeor Melire [this message]
2022-12-12 21:06   ` Mekeor Melire
2022-12-12 21:24     ` (
2022-12-15 14:26   ` Ludovic Courtès
2022-12-12 22:53 ` [PATCH guix-artwork v3] " (
2022-12-17 22:06 ` [PATCH guix-artwork v4] " (
2023-01-04 12:00   ` Ludovic Courtès
2023-01-05 12:00     ` (
2023-01-06  1:12       ` 宋文武
2023-01-09 11:13       ` Ludovic Courtès
2023-01-10  6:59         ` (
2023-01-11 21:59           ` zimoun

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=874ju0tk0c.fsf@posteo.de \
    --to=mekeor@posteo.de \
    --cc=guix-devel@gnu.org \
    --cc=paren@disroot.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.