From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] shapelib: new package
Date: Thu, 22 Sep 2016 07:19:24 +0200 [thread overview]
Message-ID: <20160922071924.7a92d39b@free-electrons.com> (raw)
In-Reply-To: <20160922034142.itfvvgp56mdxcslu@tarshish>
Hello,
On Thu, 22 Sep 2016 06:41:42 +0300, Baruch Siach wrote:
> > Either that or I update DEVELOPERS when I also update CHANGES, but not
> > everyone might want to get listed / might want to get listed without
> > being the author of the commit adding the package.
>
> A DEVELOPERS entry is probably most useful when the package is first added, as
> it starts showing up in the autobuilder. Delaying the DEVELOPERS update
> reduces its usefulness.
Exactly my thought: I want the DEVELOPERS file to be updated at the
same time as a package is added, so that as soon there are autobuilder
failures, they are directly reported to the person who contributed the
package. That's one of the big points for having this DEVELOPERS file.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2016-09-22 5:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-31 12:45 [Buildroot] [PATCH 1/1] shapelib: new package Zoltan Gyarmati
2016-09-21 13:57 ` Thomas Petazzoni
2016-09-21 16:47 ` Baruch Siach
2016-09-21 18:04 ` Thomas Petazzoni
2016-09-21 21:12 ` Peter Korsgaard
2016-09-22 3:41 ` Baruch Siach
2016-09-22 5:16 ` Peter Korsgaard
2016-09-22 7:17 ` Thomas Petazzoni
2016-09-22 7:26 ` Peter Korsgaard
2016-09-22 5:19 ` Thomas Petazzoni [this message]
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=20160922071924.7a92d39b@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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 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.