From: Mike Zick <minimod@morethan.org>
To: buildroot@busybox.net
Subject: [Buildroot] mail list details
Date: Tue, 29 Apr 2014 08:21:20 -0500 [thread overview]
Message-ID: <20140429082120.12127082@core2quad.morethan.org> (raw)
In-Reply-To: <CAAXf6LUX2p1DnyZjyzZhJE1DjnRX9oeSDTP03h8t27EY30gMpw@mail.gmail.com>
On Tue, 29 Apr 2014 14:09:00 +0200
Thomas De Schampheleire <patrickdepinguin@gmail.com> wrote:
> Hi,
>
>
> On Tue, Apr 29, 2014 at 1:44 PM, Parsa Panahi
> <panahi.parsa@paravisioner.com> wrote:
> > Hi I want to become familiar with buildroot daily mails which comes
> > to me everyday.
> >
> > I receive many emails in this format that is changing some packages
> > with some config file. for example the following is about a change
> > to opencv package to support qt5.. but I don't know how to apply it
> > to my config file, so it become updated ...
> >
If you only want to apply patches which have been reviewed -
Then select only those messages with the tag: [git commit] added
to the title line.
You can also simply update ('git pull') your local copy of the
repository after seeing the '[git commit]' tagged messages.
Other messages on this list are **proposed** patches, usually
still under discussion and review.
Those are **not** in the repository (yet), some never will be.
Those patch messages are of interest only to those who want to
participate in the review and testing process.
See also the following:
> >
>
> What is sent on the list are 'patches'. A patch is a set of lines
> representing a change to the code. See also
> http://en.wikipedia.org/wiki/Patch_%28Unix%29
>
> The typical way to start is to use a git repository and clone the
> buildroot sources. Patches can then be applied using 'git am', or
> using the standard 'patch' utility (git is recommended).
> See http://nightly.buildroot.org/manual.html#getting-buildroot and
> http://nightly.buildroot.org/manual.html#apply-patches-patchwork for
> some details.
>
> Best regards,
> Thomas
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
prev parent reply other threads:[~2014-04-29 13:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 11:44 [Buildroot] mail list details Parsa Panahi
2014-04-29 12:02 ` Baruch Siach
2014-04-29 12:09 ` Thomas De Schampheleire
2014-04-29 13:21 ` Mike Zick [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=20140429082120.12127082@core2quad.morethan.org \
--to=minimod@morethan.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.