From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] shapelib: new package
Date: Thu, 22 Sep 2016 06:41:42 +0300 [thread overview]
Message-ID: <20160922034142.itfvvgp56mdxcslu@tarshish> (raw)
In-Reply-To: <8760pprm82.fsf@dell.be.48ers.dk>
Hi Peter,
On Wed, Sep 21, 2016 at 11:12:29PM +0200, Peter Korsgaard wrote:
> >>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
> > On Wed, 21 Sep 2016 19:47:53 +0300, Baruch Siach wrote:
> >> A DEVELOPERS file update on every new package makes cherry-picking
> >> harder. For that reason, I think, Peter stopped updating the CHANGES
> >> file in every patch.
>
> > Right. What should we do then? Update the DEVELOPERS file in a separate
> > patch? But then we're going to have zillions of patches whose sole
> > purpose of to update the DEVELOPERS file. But of course, that's better
> > for cherry-picking.
>
> 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.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
next prev parent reply other threads:[~2016-09-22 3:41 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 [this message]
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
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=20160922034142.itfvvgp56mdxcslu@tarshish \
--to=baruch@tkos.co.il \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox