From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2 v4] package/mono: new package
Date: Mon, 20 Oct 2014 15:26:40 +0200 [thread overview]
Message-ID: <20141020152640.196a72a5@free-electrons.com> (raw)
In-Reply-To: <CA+TH9VmzXk=Ls-Pw7HQW8Sji71+-JQjZpuag9GuK8tmjgvgWPQ@mail.gmail.com>
Dear Angelo Compagnucci,
On Mon, 20 Oct 2014 15:08:22 +0200, Angelo Compagnucci wrote:
> > When you post new versions of the Mono patches, please post *all*
> > patches, i.e both monolite and mono. Otherwise, we don't understand
> > which version of which patch should be applied, and we don't understand
> > why we receive a single patch titled PATCH 2/2 (where is PATCH 1/2 ?).
>
> Monolite patch is not changed, should I resend all the patches also if
> not changed? It's not toot much confusion?
Yes, you should resend both patches, even if only one changed. And no,
it doesn't cause confusion: what causes confusion is to *not* resend
them both.
Of course, make sure that in the cover letter that introduces your two
patches, you write down a changelog of the changes since the previous
version. See the Buildroot manual for more details about the cover
letter.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-10-20 13:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-20 10:07 [Buildroot] [PATCH 2/2 v4] package/mono: new package Angelo Compagnucci
2014-10-20 12:59 ` Thomas Petazzoni
2014-10-20 13:08 ` Angelo Compagnucci
2014-10-20 13:26 ` Thomas Petazzoni [this message]
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=20141020152640.196a72a5@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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