From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] docs: update DEVELOPERS modification process
Date: Sun, 5 Nov 2017 09:55:29 +0100 [thread overview]
Message-ID: <20171105095529.092e08be@windsurf> (raw)
In-Reply-To: <20171105060749.p5d7vwxbdveg67ck@sapphire.tkos.co.il>
Hello,
On Sun, 5 Nov 2017 08:07:49 +0200, Baruch Siach wrote:
> > > Not sure about "or modifying". Mixing a DEVELOPERS update into a random
> > > package update does not always make sense. The manual only refers to new
> > > packages/boards. I suggest to drop this sentence entirely, and leave the
> > > details for the manual.
> >
> > Joseph is modifying the manual here, so I'm not sure what your last
> > sentence means.
>
> Ah. For some reason I had the impression that this change is against the
> DEVELOPERS file itself. So let me rephrase my suggestion:
>
> I suggest to drop this sentence entirely, and leave the details for the
> DEVELOPERS manual section.
No, I think it is good to have this sentence in the "Adding a new
package" section of the manual. Indeed new contributors are much more
likely to read this section when contributing a new package than an
obscure section specific to the DEVELOPERS file at the end of the
manual.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-11-05 8:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-03 21:10 [Buildroot] [PATCH 1/1] docs: update DEVELOPERS modification process Joseph Kogut
2017-11-04 18:53 ` Baruch Siach
2017-11-04 22:14 ` Thomas Petazzoni
2017-11-05 6:07 ` Baruch Siach
2017-11-05 8:55 ` Thomas Petazzoni [this message]
2017-11-05 7:43 ` Peter Korsgaard
2017-11-05 8:55 ` Thomas Petazzoni
2017-11-05 20:14 ` Peter Korsgaard
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=20171105095529.092e08be@windsurf \
--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.