all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: GNU Guixguix source archive branch, master, updated. v0.3-85-gda7cabd
Date: Wed, 28 Aug 2013 23:17:18 +0200	[thread overview]
Message-ID: <87d2ox7bxd.fsf@gnu.org> (raw)
In-Reply-To: <E1VEm2A-0007ez-Of@vcs.savannah.gnu.org> (Andreas Enge's message of "Wed, 28 Aug 2013 20:08:14 +0000")

Andreas Enge <andreas@enge.fr> skribis:

> commit da7cabd46b20708d083329bd7ec9fd36bf218895
> Author: Andreas Enge <andreas@enge.fr>
> Date:   Wed Aug 28 22:04:52 2013 +0200
>
>     doc: Shuffle some text around.
>     
>     * doc/guix.texi: Drop duplicate copyright notice, start section
>         "Packaging Guidelines" with existant text.

I’d prefer discussing non-trivial doc changes on the list.

(Am I in rant mode or something?  ;-))

Regarding the patch: I think the duplicate copyright notice is needed so
that it appears in the Info output.  Could you check that?

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.

WDYT?

Thanks,
Ludo’.

       reply	other threads:[~2013-08-28 21:22 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 ` Ludovic Courtès [this message]
2013-08-28 21:52   ` GNU Guixguix source archive branch, master, updated. v0.3-85-gda7cabd Andreas Enge
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87d2ox7bxd.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=andreas@enge.fr \
    --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.