From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/4] minicom: update to use latest git repository
Date: Wed, 1 Aug 2018 19:00:33 +0200 [thread overview]
Message-ID: <20180801190033.436cc1b2@windsurf> (raw)
In-Reply-To: <f8274299-4904-5968-9eb2-07d7b58bb0f3@micronovasrl.com>
Hello,
On Wed, 1 Aug 2018 17:14:42 +0200, Giulio Benetti wrote:
> >> Giulio Benetti (4):
> >> minicom: update package to use git repository.
> >> minicom: add pre-configure hook to call autogen.sh
> >> minicom: delete patches
> >> minicom: delete hash file.
> >
> > All these patches should be just one, otherwise your series is not
> > bisectable.
>
> Ah ok, I thought it was easier break all patches.
It's not about being "easy". It's about separating logical changes, one
per patch.
Here the problem of your patch series is that if I apply just PATCH
1/4, minicom no longer builds, because it doesn't do the autoreconf
tweak, the patches won't apply, and the hash file doesn't match. This
is why I said your series is "not bisectable": it doesn't build/work
between each patch of the series.
In your situation, the change to use this different download location
for Minicom is the change, and as part of the change, it is necessary
to remove patches, tweak for autoreconf and delete the hash file. This
is all one change.
> So basically the commit log will be the cover letter, right?
Yes.
> And btw, is commit log of cover letter acceptable?
There is no "commit log" in the cover letter. The commit logs are in the
patches themselves. The cover letter contains some introduction text,
and is only necessary for patch series with multiple patches, for which
additional explanations about what the whole series is doing.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-08-01 17:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-01 12:57 [Buildroot] [PATCH 0/4] minicom: update to use latest git repository Giulio Benetti
2018-08-01 12:57 ` [Buildroot] [PATCH 1/4] minicom: update package to use " Giulio Benetti
2018-08-01 12:57 ` [Buildroot] [PATCH 2/4] minicom: add pre-configure hook to call autogen.sh Giulio Benetti
2018-08-01 14:48 ` Thomas Petazzoni
2018-08-01 15:05 ` Giulio Benetti
2018-08-01 15:10 ` Thomas Petazzoni
2018-08-01 15:13 ` Giulio Benetti
2018-08-01 12:57 ` [Buildroot] [PATCH 3/4] minicom: delete patches Giulio Benetti
2018-08-01 12:57 ` [Buildroot] [PATCH 4/4] minicom: delete hash file Giulio Benetti
2018-08-01 14:47 ` [Buildroot] [PATCH 0/4] minicom: update to use latest git repository Thomas Petazzoni
2018-08-01 15:14 ` Giulio Benetti
2018-08-01 17:00 ` Thomas Petazzoni [this message]
2018-08-01 20:57 ` Giulio Benetti
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=20180801190033.436cc1b2@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox