From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] docs/manual: standardize a bit more the formatting of commit titles
Date: Mon, 26 Nov 2018 21:20:42 +0100 [thread overview]
Message-ID: <20181126202042.GM28830@scaer> (raw)
In-Reply-To: <20181125210940.2d18852f@windsurf>
Thomas, All,
On 2018-11-25 21:09 +0100, Thomas Petazzoni spake thusly:
> 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,
I'd be OK to use your proposal using the 'prefix: name: what" (even
though I find it ugly, but that's probably because I haven't been
totally tainted by the kernel yet ;-) )
So, for example:
package: busybox: bump version to 1.29.3
package: xdriver_xf86-video-siliconmotion: bump version to 1.7.9
package: uboot: switch to kconfig by default
infra: pkg-generic: fix show-build-order stdout pollution
core: legal: add package dependencies with licenses to the manifest
fs: common: drop intermediate tarball
fs: ext2: add option for lz4 compression
testing: add test for the f2fs filesystem support
[...]
arch: arm: add FPv5 support for cortex-m7
docs: manual: add external.desc to list of files needed for BR2_EXTERNAL
docs: website: update for 2018.11-rc1
misc: anything else goes here
> but
> we have never really used such 'semantic' naming so far.
Actually, that is exactly what I've been doing all those years.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2018-11-26 20:20 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
2018-11-26 20:20 ` Yann E. MORIN [this message]
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=20181126202042.GM28830@scaer \
--to=yann.morin.1998@free.fr \
--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