From: Alexander Dahl <post@lespocky.de>
To: ptxdist@pengutronix.de
Cc: Bastian Stender <bst@pengutronix.de>
Subject: Re: [ptxdist] [PATCH] beep: new package
Date: Mon, 9 Oct 2017 23:13:04 +0200 [thread overview]
Message-ID: <20171009211303.7tigjt4c2d6abvqp@falbala.home.lespocky.de> (raw)
In-Reply-To: <20171009170236.11312-1-bst@pengutronix.de>
[-- Attachment #1.1: Type: text/plain, Size: 973 bytes --]
Hei hei,
On Mon, Oct 09, 2017 at 07:02:36PM +0200, Bastian Stender wrote:
> diff --git a/rules/beep.make b/rules/beep.make
> new file mode 100644
> index 000000000..74931ca4c
> --- /dev/null
> +++ b/rules/beep.make
> @@ -0,0 +1,56 @@
> +# -*-makefile-*-
> +#
> +# Copyright (C) 2017 by Johnathan Nightingale <johnath@johnath.com>
[…]
> + @$(call install_fixup, beep,AUTHOR,"Johnathan Nightingale <johnath@johnath.com>")
On all the other ptxdist packages I saw, this was the package author,
not the upstream author. Is this supposed to be the package author aka
the one responsible for this rules/*.make file or the author of the
software packaged?
Greets
Alex
--
»With the first link, the chain is forged. The first speech censured,
the first thought forbidden, the first freedom denied, chains us all
irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie)
*** GnuPG-FP: C28E E6B9 0263 95CF 8FAF 08FA 34AD CD00 7221 5CC6 ***
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 91 bytes --]
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2017-10-09 21:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 17:02 Bastian Stender
2017-10-09 21:13 ` Alexander Dahl [this message]
2017-10-10 7:22 ` Michael Olbrich
2017-10-10 10:05 ` Bastian Stender
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=20171009211303.7tigjt4c2d6abvqp@falbala.home.lespocky.de \
--to=post@lespocky.de \
--cc=bst@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox