From: Rolf Leggewie <no2spam@nospam.arcornews.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Getting patches committed
Date: Thu, 21 Jan 2010 13:16:26 +0100 [thread overview]
Message-ID: <hj9giu$mfp$1@ger.gmane.org> (raw)
In-Reply-To: <883120D4-C490-4713-B872-F02376E88CEE@vanille-media.de>
Dr. Michael Lauer wrote:
> I fully agree. I'm neither using patchwork nor do I find patches on the list a good idea.
> I'd welcome for-oe-upstream trees that would contain patches that -- if good -- we could
> just pull from.
Yes, me too would prefer to pull another branch from somewhere and
cherry-pick from it over other solutions.
I have two questions.
1) is it possible to host such a free-for-all branch somewhere?
2) although generally not a good idea, would it be possible to rebase
this branch frequently so that the unapplied patches always come
up first in "git log"?
OE needs a stronger community culture. Too many devs are just contempt
with "my stuff works fine for me".
next prev parent reply other threads:[~2010-01-21 12:19 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 9:43 Getting patches committed Paul Menzel
2010-01-21 10:02 ` Holger Hans Peter Freyther
2010-01-21 10:20 ` Dr. Michael Lauer
2010-01-21 10:30 ` Holger Hans Peter Freyther
2010-01-21 12:15 ` Philip Balister
2010-01-21 12:36 ` Thomas Zimmermann
2010-01-21 12:45 ` Philip Balister
2010-01-21 19:06 ` Paul Menzel
2010-01-21 15:49 ` Konrad Mattheis
2010-01-21 19:10 ` Paul Menzel
2010-01-21 12:16 ` Rolf Leggewie [this message]
2010-01-21 12:34 ` Frans Meulenbroeks
2010-01-21 19:01 ` Paul Menzel
2010-01-21 19:48 ` Martin Jansa
2010-01-21 22:06 ` Stanislav Brabec
2010-01-21 22:00 ` Stanislav Brabec
2010-01-21 23:11 ` Rolf Leggewie
2010-01-22 0:13 ` Stanislav Brabec
2010-01-22 0:37 ` Rolf Leggewie
2010-01-22 0:40 ` Richard Purdie
2010-01-22 7:53 ` Holger Hans Peter Freyther
2010-01-22 11:44 ` Petr Štetiar
2010-01-22 14:53 ` Rolf Leggewie
2010-01-22 16:15 ` Petr Štetiar
2010-01-22 16:44 ` Rolf Leggewie
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='hj9giu$mfp$1@ger.gmane.org' \
--to=no2spam@nospam.arcornews.de \
--cc=openembedded-devel@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 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.