From: Pierre-Antoine Rault <par@rigelk.eu>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [patch] - Packaging guideline documentation update
Date: Tue, 11 Mar 2014 00:10:56 +0100 [thread overview]
Message-ID: <531E4680.1050307@rigelk.eu> (raw)
In-Reply-To: <87k3c1lqmr.fsf@gnu.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
On 10/03/2014 21:56, Ludovic Courtès wrote:
> I’ve applied a stripped-down version of the patch: I ended up
> removing “Packaging 101” because it was redundant with the
> “Packaging Guidelines” section of the manual, so I moved the
> missing bits in that section (info "(guix) Packaging Guidelines").
> I also removed details about how ‘git format-patch’ and co. work,
> because these commands already have their own manual.
I admit it was overkill :)
> I realize the manual can be improved when it comes to introductory
> material.
I would think of a (not so) short explaination of the guix tree as
seen in the GNUnet manuel, for instance. What do you think ?
- - rigelk
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJTHkaAAAoJEHfJ0QE7gLd6XSsIAIX5kQtsZmdJ6P8kSRo+0Euo
YolTVuBs1BGbEq+sIx1nBPpzt1CYCuLkO/R/FzbKNpy2RmHwR/M2K1OEcr71hH2B
DFIW65WEkTAZeouDRmU06leg+9I3EkQpJ6rqRmIyts9drUzRQoJdzkn0uZAROvSN
hqBofvBQGvurvbBg+bjIW9UqObowsa9Bhg8lH0bLWpqA2CIzw8U3uWPTphHc5azH
ML7lNYtdr7J95yMXsl/PN2DpiWiO8pG+uXPmBUanCgmipcAW5tU1VmC9Jp+LJBPU
h1ke6Ym0wFsyFwuqzqC3INcOkwvGeM9yO7D/XNHVlQusY+FyRIkbEGeHyVkQ3Eg=
=tuXM
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-03-10 23:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-09 16:46 [patch] - Packaging guideline documentation update Pierre-Antoine Rault
2014-03-10 20:56 ` Ludovic Courtès
2014-03-10 23:10 ` Pierre-Antoine Rault [this message]
2014-03-11 8:57 ` Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2014-03-11 12:53 Pierre-Antoine Rault
2014-03-11 13:08 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=531E4680.1050307@rigelk.eu \
--to=par@rigelk.eu \
--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 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.