Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] qt: Allow enabling of QtWebKit with GCC 6+
Date: Tue, 24 Oct 2017 08:15:34 +0200	[thread overview]
Message-ID: <87r2tt5awp.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <4881796E12491D4BB15146FE0209CE6467F9F640@DE02WEMBXB.internal.synopsys.com> (Alexey Brodkin's message of "Tue, 17 Oct 2017 15:02:39 +0000")

>>>>> "Alexey" == Alexey Brodkin <Alexey.Brodkin@synopsys.com> writes:

Hi,

 >> Committed to 2017.08.x, thanks.

 > I see that commit was applied on 2 "LTS" branches already which is definitely good.
 > But my question is are there any formal rules and guidelines for patches to be
 > cherry-picked onto LTS branches? Something like
 > https://github.com/torvalds/linux/blob/master/Documentation/process/stable-kernel-rules.rst?

As discussed during the dev days, we don't really have any format
rules. If you think specific patches should be backported, please let me
know.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2017-10-24  6:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-22 12:50 [Buildroot] [PATCH] qt: Allow enabling of QtWebKit with GCC 6+ Evgeniy Didin
2017-10-03 19:59 ` Thomas Petazzoni
2017-10-14  7:49 ` Peter Korsgaard
2017-10-17  9:02 ` Peter Korsgaard
2017-10-17 15:02   ` Alexey Brodkin
2017-10-24  6:15     ` Peter Korsgaard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-09-19  9:14 Evgeniy Didin
2017-09-19 16:41 ` Thomas Petazzoni
2017-09-19 19:37 ` Arnout Vandecappelle

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=87r2tt5awp.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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