From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Orangepi-PC Diff: What should I apply this against?
Date: Fri, 25 Dec 2015 19:57:36 +0100 [thread overview]
Message-ID: <20151225195736.456f0366@free-electrons.com> (raw)
In-Reply-To: <567D8C8E.6010802@klouds.org>
Dear Jacob Gadikian,
On Sat, 26 Dec 2015 01:35:58 +0700, Jacob Gadikian wrote:
> Hi, pretty amateurish question, but I'm not sure what verson of
> Buildroot to apply these diff files to-- I'm even guessing that is
> somehow indicated in the diff, but well, I'm not getting it. Anyone
> care to enlighten me?
Usually, people send patches that apply to the latest version of
Buildroot available from the Git repository, i.e the latest state of
the master branch.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-12-25 18:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-25 18:35 [Buildroot] Orangepi-PC Diff: What should I apply this against? Jacob Gadikian
2015-12-25 18:57 ` 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=20151225195736.456f0366@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