From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/6] tini: new package
Date: Sun, 15 Jul 2018 21:58:06 +0200 [thread overview]
Message-ID: <20180715195806.GH2516@scaer> (raw)
In-Reply-To: <CA+h8R2oxXWWnPT8dnn0Bt4UL=JA8SGjDg3vCyZNNchrPCaWJ+w@mail.gmail.com>
Christian, All,
On 2018-07-15 12:26 -0700, Christian Stewart spake thusly:
> Hi Yann,
> On Sun, Jul 15, 2018 at 9:01 AM Yann E. MORIN < [1]yann.morin.1998@free.fr> wrote:
>
> Since you want to do a static build (which I questioned in my previous
> reply), you should depend on static libs being actually available,
> i.e.:
>
> ? ? depends on !BR2_SHARED_LIBS # Static build
>
> I went over this with Thomas before the last time I tried to merge a similar series.
> Here are the relevant bits:
[--SNIP--]
Then why did you not add those explanation in the commit log, in this
new iteration?
Personally, I don't care about a commit log that says "hey, let's add a
new package". That is pretty much obvious from the diffstat itself.
What a commit log is here for, is to explain the tricky details of why a
specific technical solution is used, especially when it is not obvious
that it works, and more especially when it runs contrary to the usual
and common knowledge/wisdom.
Then, when we need to look back at the code in the (far!) future, and we
wonder "how on Earth can this even work to begin with?", we can git-blame
or git-log the file and see the corresponding commit and commit log, and
understand that litle detail. Because by then, the post on the mailing
list about a comment on the nth-previous iteration will be long
forgotten.
> Either way, this part of the series is not important. I'm happy to respin it with just the docker-cli and docker-engine split
> (caused originally by trying to upgrade docker-engine).
Yes, please do so: untangle the two and bump them, since this is not very
controversial.
But still, I'd like to understand why we need to have the host provide
an init to the guest, and why can't the guest be responsible for
providing its own init... Sorry if you already replied to that in
another thread... In which case those explanations would have been great
to be repeated in the commit log itself.
Thanks! :-)
Regards,
Yann E. MORIN.
> Best,
> Christian Stewart
>
> Links:
> 1. mailto:yann.morin.1998 at free.fr
--
.-----------------.--------------------.------------------.--------------------.
| 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-07-15 19:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-15 1:07 [Buildroot] [PATCH 1/6] tini: new package Christian Stewart
2018-07-15 1:07 ` [Buildroot] [PATCH 2/6] dumb-init: " Christian Stewart
2018-07-15 1:07 ` [Buildroot] [PATCH 3/6] docker-engine: add support for init processes Christian Stewart
2018-07-15 1:07 ` [Buildroot] [PATCH 4/6] runc: bump to 69663f0b Christian Stewart
2018-07-15 1:07 ` [Buildroot] [PATCH 5/6] docker-containerd: bump to v1.1.1 Christian Stewart
2018-07-15 1:07 ` [Buildroot] [PATCH 6/6] docker-engine: split into docker-{cli, engine}, bump v2018.06-ce-rc3 Christian Stewart
2018-07-15 1:07 ` [Buildroot] [PATCH v3 1/6] tini: new package Christian Stewart
2018-07-15 14:30 ` Matthew Weber
2018-07-15 16:01 ` Yann E. MORIN
2018-07-15 19:26 ` Christian Stewart
2018-07-15 19:58 ` Yann E. MORIN [this message]
2018-07-16 22:19 ` Arnout Vandecappelle
2018-07-15 1:07 ` [Buildroot] [PATCH v3 2/6] dumb-init: " Christian Stewart
2018-07-15 1:07 ` [Buildroot] [PATCH v3 3/6] docker-engine: add support for init processes Christian Stewart
2018-07-15 1:07 ` [Buildroot] [PATCH v3 4/6] runc: bump to 69663f0b Christian Stewart
2018-07-15 1:07 ` [Buildroot] [PATCH v3 5/6] docker-containerd: bump to v1.1.1 Christian Stewart
2018-07-15 1:07 ` [Buildroot] [PATCH v3 6/6] docker-engine: split into docker-{cli, engine}, bump v2018.06-ce-rc3 Christian Stewart
2018-07-15 15:57 ` [Buildroot] [PATCH 1/6] tini: new package Yann E. MORIN
2018-08-10 13:53 ` Matthew Weber
2018-08-10 22:36 ` Christian Stewart
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=20180715195806.GH2516@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