From: Ola Redell <ola.redell@retotech.se>
To: openembedded-core@lists.openembedded.org
Subject: questions on patching
Date: Tue, 3 Jan 2017 16:21:30 +0100 [thread overview]
Message-ID: <80e2a281-3a69-3ea6-e46a-01b56acc947a@retotech.se> (raw)
Hi all,
I am a bit new to sending in patches to a list like this and
specifically to OE-core, so I need a bit of guidance.
I have a fix for a bug I found in Jethro in the kernel.bbclass and I
have tested my fix there (update-alternatives needs a full path also
when removing an alternative). Now, the bug is around in many different
branches (laverne, krogoth and master for sure) but that particular
patch will only apply to Jethro.
I can make a patch for master but would have problems testing it
thoroughly there without spending quite a bit of time (which I don't
have at the moment).
Easy questions:
How should I proceed?
How do I know what branches are actively maintained and for which
patches are welcome?
I should have asked these questions before sending my earlier patch for
the kernel-module-split.bbclass since this holds for that too.
Thanks,
Ola
next reply other threads:[~2017-01-03 15:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-03 15:21 Ola Redell [this message]
2017-01-03 17:13 ` questions on patching Khem Raj
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=80e2a281-3a69-3ea6-e46a-01b56acc947a@retotech.se \
--to=ola.redell@retotech.se \
--cc=openembedded-core@lists.openembedded.org \
/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