From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] docs/manual: standardize a bit more the formatting of commit titles
Date: Sun, 25 Nov 2018 21:09:40 +0100 [thread overview]
Message-ID: <20181125210940.2d18852f@windsurf> (raw)
In-Reply-To: <20181125161722.GC28830@scaer>
Hello,
On Sun, 25 Nov 2018 17:17:22 +0100, Yann E. MORIN wrote:
> When I add 'package/' as a prefix, it is not because it is in the
> package subdirectory, but because it is touching a package, as opposed
> to something else, like core stuff or package infrastructures.
>
> The prefix is a 'semantic' prefix, not a path prefix. A path prefix
> serves no purpose in and of itself.
I don't quite agree. If we really want to use 'semantic' prefix, then
we should do:
package: foo: bump version to ...
Using 'package/foo' really looks way too much like a path, and
therefore...
> There, I would have sued 'infra/' as a prefix, because it is touching
> the pkg0generic infrastructure, not a package.
this doesn't make much sense to me, because there is nothing named
infra/pkg-generic in the tree. "infra: pkg-generic: " would be OK, but
we have never really used such 'semantic' naming so far.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-11-25 20:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-24 10:19 [Buildroot] [PATCH] docs/manual: standardize a bit more the formatting of commit titles Thomas Petazzoni
2018-11-25 1:16 ` Carlos Santos
2018-11-25 8:51 ` Peter Korsgaard
2018-11-25 8:56 ` Peter Korsgaard
2018-11-25 9:45 ` Thomas Petazzoni
2018-11-25 16:17 ` Yann E. MORIN
2018-11-25 20:09 ` Thomas Petazzoni [this message]
2018-11-26 20:20 ` Yann E. MORIN
2018-11-26 20:25 ` Thomas Petazzoni
2018-12-01 20:15 ` Yann E. MORIN
2019-01-16 8:30 ` 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=20181125210940.2d18852f@windsurf \
--to=thomas.petazzoni@bootlin.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.