From: Andreas Enge <andreas@enge.fr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: GNU Guixguix source archive branch, master, updated. v0.3-85-gda7cabd
Date: Wed, 28 Aug 2013 23:52:28 +0200 [thread overview]
Message-ID: <20130828215228.GA27907@debian> (raw)
In-Reply-To: <87d2ox7bxd.fsf@gnu.org>
On Wed, Aug 28, 2013 at 11:17:18PM +0200, Ludovic Courtès wrote:
> I’d prefer discussing non-trivial doc changes on the list.
I considered them trivial, since the information has not been altered,
just slightly reorganised.
> Regarding the patch: I think the duplicate copyright notice is needed so
> that it appears in the Info output. Could you check that?
Indeed, so I should add it again.
> About the structure: I thought an “Adding New Packages” section that
> would include both the licensing requirements and technical advice made
> sense, on the grounds that contributors-to-be need to see all of that.
>
> Rules as suggested by Cyril could go under “Adding New Packages” (and
> not “Packaging Guidelines”, as I initially wrote), in appropriate
> sub-sections.
I find the title "Packaging Guidelines" snappier. And before, there was
a subsection "Packaging Guidelines" inside the section "Adding New Packages",
so we would have ended up with subsubsections containing the different
items. Now it is one level flatter. And still everything that was in
"6.3 Adding New Packages" is in "6.3 Packaging Guidelines", so not much
changed really. The license requirements are in "6.3.1 Software Freedom",
the technical points should become 6.3.2 and so on.
Andreas
next prev parent reply other threads:[~2013-08-28 21:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1VEm2A-0007ez-Of@vcs.savannah.gnu.org>
2013-08-28 21:17 ` GNU Guixguix source archive branch, master, updated. v0.3-85-gda7cabd Ludovic Courtès
2013-08-28 21:52 ` Andreas Enge [this message]
2013-08-29 20:17 ` Ludovic Courtès
2013-08-29 20:41 ` Andreas Enge
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=20130828215228.GA27907@debian \
--to=andreas@enge.fr \
--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).