unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: dannym@scratchpost.org, guix-devel@gnu.org, ludo@gnu.org
Subject: Re: [PATCH] gnu: dtc: Make home-page field value more useful.
Date: Tue, 31 Jan 2017 00:48:02 +0100	[thread overview]
Message-ID: <0bfc2689-f2a2-2437-fdd4-c6d29268f6e5@tobias.gr> (raw)
In-Reply-To: <20170125093713.14314-1-dannym@scratchpost.org>


[-- Attachment #1.1: Type: text/plain, Size: 707 bytes --]

Danny,
Ludo',

On 25/01/17 10:37, Danny Milosavljevic wrote:
> -    (home-page "https://www.devicetree.org")
> +    (home-page "http://elinux.org/Device_Tree_Usage")

That link is a great HOWTO for writing device tree source files, but
it's not the _dtc_ home page.

In fact, it doesn't mention ‘dtc’ or the actual compilation anywhere.

If we really want to point users here, how about:

  (description "@command{dtc} compiles
  @uref{http://elinux.org/Device_Tree_Usage, device tree source files}
  to device tree binary files. These are board description files used
  by Linux and BSD.")

dtc does look rather homeless, but that's a different problem.

Kind regards,

T G-R


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 476 bytes --]

  parent reply	other threads:[~2017-01-30 23:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-25  9:37 [PATCH] gnu: dtc: Make home-page field value more useful Danny Milosavljevic
2017-01-30 22:44 ` Ludovic Courtès
2017-01-30 23:48 ` Tobias Geerinckx-Rice [this message]
2017-01-31  8:06   ` [PATCH v2] gnu: dtc: Update description to reference HOWTO Danny Milosavljevic
2017-01-31 16:34     ` Marius Bakke
2017-02-01 12:53       ` Danny Milosavljevic

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=0bfc2689-f2a2-2437-fdd4-c6d29268f6e5@tobias.gr \
    --to=me@tobias.gr \
    --cc=dannym@scratchpost.org \
    --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).