All of lore.kernel.org
 help / color / mirror / Atom feed
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 10:45:53 +0100	[thread overview]
Message-ID: <20181125104553.3f24be17@windsurf> (raw)
In-Reply-To: <1442786873.3545705.1543108593942.JavaMail.zimbra@datacom.com.br>

Hello,

On Sat, 24 Nov 2018 23:16:33 -0200 (BRST), Carlos Santos wrote:

> Looks good, but isn't "package/" a bit superfluous, since Most of the
> commits are for packages? It also goes against the tradition:
> 
> $ git log --oneline origin/master | grep -i '^.......... [^ /]*: bump' |wc -l
> 7644
> $ git log --oneline origin/master | grep -i '^.......... [^ ]*/[^ ]*: bump' |wc -l
> 2296

Yes, I agree the tradition has been without package/. I myself used to
prefer without package/. However, it is not very consistent, as then
when we have boot/uboot, is it about package/boot/uboot ? Or when we
have core: <something>, is it about the package "core" ?

While I was personally not adding package/, I saw others doing it, and
ultimately found it more consistent.

> BTW, I want the bike shed red.

Red is not too bad :-)

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  parent reply	other threads:[~2018-11-25  9:45 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 [this message]
2018-11-25 16:17 ` Yann E. MORIN
2018-11-25 20:09   ` Thomas Petazzoni
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=20181125104553.3f24be17@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.