From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/qwt : prepared package for other versions of Qt.
Date: Sat, 26 Mar 2016 13:35:39 +0100 [thread overview]
Message-ID: <56F6821B.70902@mind.be> (raw)
In-Reply-To: <56F56464.8050204@yahoo.fr>
On 03/25/16 17:16, David Picard wrote:
> I saw you merged the patches into the master branch. So should I make a new
> patch based on the current master, or issue a new version of the 2 previous
> patches ?
A new patch based on the master.
How else could it be applied? If you create a new version of the previous
patches, the ones that are already committed would have to be reverted first,
making things unnecessarily complicated.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2016-03-26 12:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 20:19 [Buildroot] [PATCH 1/2] package/qwt : prepared package for other versions of Qt David Picard
2016-03-24 20:19 ` [Buildroot] [PATCH 2/2] package/qwt : added support for Qt5 David Picard
2016-03-25 9:51 ` Thomas Petazzoni
2016-03-25 11:08 ` David Picard
2016-03-25 9:48 ` [Buildroot] [PATCH 1/2] package/qwt : prepared package for other versions of Qt Thomas Petazzoni
2016-03-25 14:46 ` David Picard
2016-03-25 15:30 ` Thomas Petazzoni
2016-03-25 16:16 ` David Picard
2016-03-26 12:35 ` Arnout Vandecappelle [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-03-24 13:36 David Picard
2016-03-16 17:37 David Picard
2016-03-20 22:13 ` Thomas Petazzoni
2016-03-20 22:18 ` Thomas Petazzoni
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=56F6821B.70902@mind.be \
--to=arnout@mind.be \
--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